应用程序故障转移大约需要45秒。
边界附近的点对程序故障更加敏感。
Points near domain boundary are more sensitive to program faults than other points.
当发生系统或应用程序故障时管理客户机。
The clients are administrated in the event of system or application failure.
在尝试诊断应用程序故障时可以使用这些报告。
These reports are intended for use by someone attempting to diagnose an application failure.
我们没有关注的是拥堵可能会导致我们的应用程序故障。
We don't have to be concerned that Clog may cause a fault in our application.
数据库服务器的故障被证明是所有应用程序故障的关键点。
The single point of failure then turns out to be the database server which takes all the applications off line when it goes down.
应用程序管理器遭遇一个固有程序故障导致无法继续执行。
Application manager threw an uncaught exception The application manager event thread threw an uncaught exception and cannot continue execution.
如果你发现了一个程序故障，但很容易就能解决的，那就把它留到第二天早上再处理吧。
If you find a programming bug and see that it will be an easy fix, you just leave it for the next morning.
有了应用程序故障转移，任何未处理的请求(来自任何来源)将在代理主服务器上被处理。
With application failover, any unprocessed requests (from any source) will be processed on the acting primary server.
这样一来，如果Gearman守护程序故障，它就可以在重启后重新创建这个工作队列。
Thus, if the Gearman daemon fails, it can recreate the work queue on restart.
如果属于这种情况，则此缺陷可能导致内存损坏或程序故障，但某些情况可能会导致可利用的安全漏洞。
If this is the case, this defect is likely to cause a memory corruption or program crash, although some cases might cause an exploitable security hole.
n层Web应用程序的典型问题与其他应用程序无异：启动时间过长、整体性能较差、无法解决某些具体问题以及应用程序故障。
The standard problems in n-tier Web applications are the same as those for any application: long startup times, poor overall performance, poor performance in specific cases, and application failures.
这个故障是由脚本程序出错造成的。
在下面的清单6中，故障处理程序通过相应的一组元素(第36行)定义了它试图处理的故障集。
The fault handler in Listing 6 below defines the set of faults it attempts to handle via a corresponding set of elements (line 36).
如果测试失败，就报告错误消息，指出故障点，同时程序执行中断。
If a test fails, an error message is reported, indicating the point of failure, and program execution halts.
页清除程序太少会使故障恢复时间变长。
Too few page cleaners increases recovery time after failures.
捕获系统级异常的故障处理程序。
这些脚本可以启动和停止程序，但是不能在程序出现故障时自动重启程序。
These scripts can start and stop a program, but they do not automatically restart the program if it fails.
在出现了应用程序或后端故障时，是否能够快速恢复运行？
Could you be back up and running quickly after experiencing an application or backend failure?
高可用性是在系统、组件或者应用程序发生故障时快速恢复基本服务的系统管理策略。
High availability is the system management strategy of quickly restoring essential services in the event of system, component, or application failure.
作用域的故障处理程序可能使用补偿处理程序来撤销这个作用域中进行的操作。
A fault handler of a scope may make use of compensation handlers to undo actions performed within that scope.
他们需要分隔实例以及同时运行两台服务器的理由就是为了降低多个并发应用程序发生故障的可能性。
The reason they wanted to separate the instances and have both servers running was to decrease the possibility of multiple concurrent application failures.
这将帮助您避免产品应用程序的调试和故障排除。
This helps you save debugging and troubleshooting time with production applications.
越多的复杂度和分层被涉及到，就越难以为一个应用程序排除故障。
The more complexity and layers that are involved, the more difficult it is to troubleshoot an application.
这种测试可能包括譬如通过测试来查看应用程序在故障转移的情况下如何响应。
This testing might include, for example, testing to see how the application responds in a failover situation.
高可用性系统将软件和工业标准硬件相结合，在系统、组件或应用程序发生故障时快速恢复来使停机时间最小化。
High availability systems combine software with industry-standard hardware to minimize downtime by quickly restoring services when a system, component, or application fails.
毫无疑问，由于是公共的JVM，所以应用程序间的故障保护是有限的。
Of course, failure protection between applications is limited, due to the common JVM.
请注意此位置必须是一个可写位置，否则此应用程序就会出现故障。
Note that this must be a writeable location otherwise the application will fail.
考虑基于云的应用程序的故障设计尤其重要。
It is particularly important to consider design for failure for your cloud-based applications.
考虑基于云的应用程序的故障设计尤其重要。
It is particularly important to consider design for failure for your cloud-based applications.
应用推荐