Problem scenario: blocked managed-task resources.
问题场景：阻塞托管任务资源。
Problem scenario: heavy workload versus limited resources.
问题场景：高工作负载与有限资源。
The tool collects relevant information for a problem scenario to help understand the root cause of the problem faced by a client.
此工具为问题场景收集有关信息以帮助了解客户端所面临的问题的根本原因。
Customers want to be able to move seamlessly from diagnosing a router problem to a helpdesk scenario to user management to a disk problem scenario, all by navigating around.
用户要求能够地从诊断路由器的问题天衣无缝地转移到求助信息状态，再到用户管理，再到磁盘问题状态等，所有这些都通过漫游实现。
However, the most practical format for the data collected will depend on the unique combination of the actual problem scenario, the options selected, and the users performing the analysis.
然而，所收集的数据最实用的格式将取决于实际问题情形的独特组合、选取的选项和执行分析的用户。
You can also profile applications as they are launched by automated testing tools, which frees you from having to repeatedly run the problem scenario and can simulate the load on the application.
您也可以在使用自动化测试工具运行应用程序时进行分析，这样可以让您很容易地重复运行有问题的场景并模拟应用程序的实际负荷。
Scenario 3: a developer receives a defect ticket for a problem encountered in a functional test cycle.
情况3：开发人员收到了一张关于功能测试周期中遇到的问题的缺陷清单。
This sample scenario requires that you send notifications to the patient whenever a home health event is processed, and to the patient's doctor whenever there is a problem.
这个样例场景要求您在处理一个家庭健康事件时向病人发送通知，而当出现一个问题时，向病人的医生发送一个通知。
The next part will introduce a typical business scenario with a typical business problem, after performing the business analysis, it will shows why WBSF can provide a solution to fix this problem.
下一部分将介绍带有典型业务问题的典型业务场景，执行业务分析之后，将展示WBSF能够提供解决方案来解决此问题的原因。
Fixed a problem of excessive CCRPC process creation during high concurrent load test scenario.
修复高共时负载测试场景期间过剩CCRPC过程创建的问题。
This section describes example scenario 3 that generates a dependency problem, and it describes how to resolve the problem.
本节将会描述产生依赖性问题的示例场景3，并讲解如何解决该问题。
Returning to the car scenario, suppose that you have a problem with your headlights.
现在回到汽车场景中，假设您的车头灯有问题。
An SVT tester develops a good test scenario to effectively exercise the feature, armed with a solid understanding of the feature, its related features, and the problem it intends to address.
SVT测试人员开发出好的测试场景，以便高效地演习该特性，这需要全面地了解特性及其相关的特性、以及它打算解决的问题。
While the data is analyzed, rules might be applied, predictive or optimization models incorporated, and different forms of output produced depending on the scenario or problem being solved.
在分析数据的同时，可能需要应用规则，需要添加预测性或优化模型，并会得到不同形式的结果，这都取决于当时的场景和要解决的问题。
When taking a trace, try to use the smallest scenario possible to reproduce your problem; otherwise, the amount of data that is captured might be prohibitive.
当进行跟踪时，应尽量使用最小的场景来再现问题；否则，被捕捉的数据量可能会令人生畏。
Getting back to our original scenario, let's say that you and your team decide that using specific directories is the most extensible solution to your build-time problem.
回到最初的场景中，假设您和您的团队认为使用特定目录是针对构建时间问题的最具扩展性的解决方案。
This article USES the following sample scenario as the basis for our problem statement and its proposed solution.
本文将以下实例场景作为问题描述及解决方案的基础。
Each scenario is further broken down into "realizations" which are specific development tasks designed to solve a particular problem.
每个场景被进一步拆分为多个“实现”，所谓“实现”，是指专门用来解决某个特殊问题的特定开发任务。
This scenario is for illustrative purposes only to highlight key IGAA features, and does not necessarily describe all details of an actual problem situation.
这个场景仅用于说明关键的IGAA特性，而没有描述实际问题情况的所有细节。
One problem with this scenario is that under differing circumstances, one woman's beta is another one's alpha.
这种借口有一个问题，就是在不同的场合，一个女人的“二号男”将是另一个女人的“一号男”。
This section describes example scenario 4 that generates a dependency problem, and it describes how to resolve the problem by setting the DB CFG parameter AUTO_REVAL to DEFERRED_FORCE.
本节描述的示例场景4 中出现了一个依赖性问题，可通过将DBCFG 的 AUTO_REVAL参数设置为 DEFERRED_FORCE 来解决此问题。
Scenario 2: Drill down on a database transaction problem.
场景2：向下钻取数据库事务问题的详细信息。
Scenario 4: Solving a cluster performance problem, from-the-field.
场景4：通过实践解决集群性能问题。
When approaching a problem, utilize "what if..." questions to consider each possible scenario.
当解决一个问题时，利用“如果…”。
The following assumptions set the scenario for the fictitious problem the application solves
下列假设为应用程序解决的虚构问题设置了场景
If one of the methods had taken considerably longer in elapsed time, You might look at this particular portlet and scenario as a potential performance problem.
如果方法之一在已用时间中占用了相当长的时间，则您可能将此特定的Portlet和场景作为潜在的性能问题来进行了解。
Another potential problem, which may seem like an unlikely scenario but actually happened to me, was a deadlock that caused Rational Software Architect to hang.
另一个对我们来说看似不可能发生但却真实发生的问题是，会出现使得Rational Rational Soft ware Architect挂起的僵局。
When selecting a problem category, all the experimental scenarios that belong to the problem category will be shown in the scenario list.
当选择某个问题类别后，属于这一问题类别的所有试验场景都将显示在Scenario list中。
For example, because a hung thread might occur when a wait leak, excessive synchronization, or a deadlock scenario takes place, the hung thread problem consists of three scenarios.
例如，在出现等待leak、过量同步或死锁时会发生hung线程，因此hung线程问题包含这三种场景。
In this priority inversion scenario, a lower-priority task holds a resource that a higher-priority task requires. (this problem occurred on Mars in the Pathfinder probe using Wind River's VxWorks.)
在这个优先级反转场景中，低优先级的任务占有着高优先级任务需要的资源(这个问题出现在使用风河公司VxWorks系统的火星开拓者探测器上)。
应用推荐