让我们来看一个典型的桌面应用程序问题。
在开发周期中越早开始测试，您就能越早地检测到应用程序问题并正确地处理它。
The earlier testing is started in the development lifecycle, the sooner application issues can be detected and properly dealt with.
对于诊断多种应用程序问题，特别是崩溃问题，内核文件起到关键作用。
Core files are vital in diagnosing many types of application problems, particularly crashes.
开发人员希望通过门户网站社区寻求在设计与构建门户网站应用程序问题上的共识。
Within the portal community, developers are want to find consensus in designing and building portal applications. Consequently, this article addresses.
当然，为有助于支持应用程序，症状数据库应该尽可能多的捕捉应用程序问题或症状。
Of course, to be a useful support application, a symptom database should capture as many application problems or symptoms as possible.
在极少数情况下，在多个JVM配置中可能出现在单个JVM配置中不可能出现的应用程序问题。
On rare occasions, application issues can arise in the multiple JVM configuration that are not possible in the single JVM configuration.
可惜的是，在日常的硬件问题和应用程序问题的折磨之下，支持人员在精疲力尽地想要跟上变更的步伐。
Sadly, with the daily grind of hardware issues and application problems, support personnel can be run ragged trying to keep up.
这正是让我们能够在不同的机器上重现和重新产生任何应用程序问题的原因，不管这台机器是虚拟的还是物理存在的。
This is what allows us to replay and reproduce any application issue on a different machine, regardless as to whether that machine is virtual or physical.
这些设置更适合于生产实例；在开发或测试实例上，您可能不希望做这些变更，因为它会使得应用程序问题的调试变得更难。
These settings are more appropriate for production instances; on development or testing instances, you may not want to make these changes as it can make it more difficult to debug application issues.
通过在分布的客户应用程序堆栈中捕获端对端的事件，并使之相互关联，该工具提供更多的分布式应用程序问题的结构化分析。
By capturing and correlating end-to-end events in the distributed stack of a customer application, this tool provides a more structured analysis of distributed application problems.
项目团队应该评估在生产环境中出现问题的应用程序的体系结构的可靠性。
The project team should assess the architectural soundness of applications that turned out to be troublesome in a production environment.
我们终于意识到问题的严重性，并通过支持和改进一系列工具、应用程序和方法以防止骗子得逞。
We are finally waking up to the severity of the problem by supporting and developing a group of tools, apps and approaches intended to prevent scammers from getting through.
如果您对上述一个或多个问题的回答是肯定的，那么您需要考虑如何处理应用程序中的时间问题。
If you answered yes to one or more of the above, then you need to think about how you handle the matter of time in your application.
在几分钟之内，ARE 就能发现并修复（没错，ARE能够为您修复问题）导致应用程序失败的权限问题。
So in a matter of minutes, ARE can find and fix (yes, it can correct issues for you!) the authority issue that is causing your application to fail.
和上面描述的场景一样，假定您在尝试解决应用程序挂起的问题。
As in the scenario described above, suppose you are trying to resolve an application hang.
如果实现得不好，将导致包括性能问题、死锁以及异常的应用程序行为等各类问题。
Implemented badly, this can lead to all types of issues, from performance problems to deadlocks to unexpected application behavior.
对于这类情况，需要重新设计应用程序才能避免问题。
For such cases, you want to redesign the application to avoid the problem.
虽然，几乎可以肯定，每个组织中的问题和症状都各不相同，但是中间件应用程序环境问题的根源却基本不变。
While the problem manifestation and symptoms almost certainly vary across organizations, the root causes of many problems in middleware application environments usually hold steady.
当您跨越多个服务器分散应用程序时，问题出现了，即如何分配输入更新。
When you spread the application out across multiple servers, the problem arises of how to distribute incoming requests.
应用程序有内存泄漏问题。
XML还非常具有灵活性，这使它成为解决中间件和应用程序异构问题的最合适的标准。
XML is also very flexible, which positions it as the most suitable standard for solving middleware and application heterogeneity problems.
事实上，一个好的习惯是假设应用程序存在问题，然后进行运行时分析以找到问题所在。
In fact, it is a good practice to assume that there is a problem, and then use runtime analysis to pinpoint what it is.
但如果在不同的应用程序中，问题可能就会，一个页面应当显示多少条结果？
But across different applications, questions might arise. How many results should you display per page?
域对象建模应用程序的问题域。
记住这个原则：“使主程序尽量简单，而将复杂的业务作为类放到库中”。它将帮助你解决测试GUI应用程序的问题。
The idea of keeping the main program very simple and putting the business complexity into classes contained in a library can also help solve the problem of testing GUI applications.
这种观点非常狭隘，并且如果被错误使用，将引发应用程序的性能问题。
That's a very limited view, and it can cause performance problems in applications if it's misapplied.
只有在编写应用程序之后，问题的性质、范围和微妙之处才会逐渐清晰起来。
Invariably, the subtleties, nuances, and scope of the problem at hand become clear only after the application has been written.
可以把这个文件传输到调试环境中，使用它判断和解决应用程序的问题。
The file can then be transmitted to a debug environment, and can be used to identify and resolve a problem with the application.
我们的应用程序可能受到这些问题的影响。
部署一个服务器端的应用程序时，问题就更为严峻。
This problem is especially serious when deploying server-side applications.
应用推荐