Designing a concurrent blocking queue with timeouts.
设计有超时限制的并发阻塞队列。
The pthreads implementation supports both blocking and timeouts.
pthreads实现既支持阻塞也支持超时。
In this example, 430d is the semaphore name, and 58 is the number of timeouts.
在这个例子中，430d是信号量名称，58是超时的数量。
If timeouts are not expected, then throwing an exception might be a better choice.
如果预料不会超时，则引发异常可能是一种更好的选择。
Business calendars can then be used for durations or timeouts in WebSphere Process Server.
然后可以将业务日历用于WebSphereProcessServer中的持续时间或超时。
A signal thread handles alarms and forces timeouts on connections that have been idle too long.
一个信号线程处理警报并在闲置时间过长的连接上强制执行超时。
When timeouts are expected, the cost of checking for null is lower than the cost of catching an exception.
当预料会超时的时候，检查是否为null的成本低于捕获异常的成本。
This setting helps the server ramp up smoothly, without having connection timeouts during the ramp-up phase.
该设置帮助服务器顺利地完成自举，在自举阶段不存在连接超时。
Table 3 shows the default thread pool sizes and inactivity timeouts for the most commonly tuned thread pools.
表3列出了最常调优的线程池的默认线程池大小和静止超时。
The examples above merely scratch the surface on timeouts, which shows how ubiquitous timeouts are in any solution.
上述示例仅仅是触及了超时的表层，展示了所有解决方案中普遍存在的超时。
The lock escalations, lock timeouts and deadlocks will indicate some potential problems in your system or application.
锁升级、锁超时和死锁将表明系统或应用程序中存在某些潜在问题。
Based on this idea, let's look at the concept of a concurrent queue where push and pop operations come with timeouts.
根据这个概念，我们来看看如何给并发队列的添加和取出操作增加超时限制。
Figure 4 presents a somewhat ideal solution, because some of the components might not support dynamically setting timeouts.
图4展示的是理想化的解决方案，因为某些组件可能不支持动态设置超时。
Connectivity issues usually surface as timeouts reported in error logs or sometimes as error messages in the user interfaces.
连通性通常表现为错误日志中报告的超时，有时也表现为用户界面中的错误消息。
Process exceptions are often caused due to temporary errors such as connectivity failure, timeouts, or design time code errors.
流程异常的原因通常是一些临时错误，比如连通性故障、超时、或设计时代码错误。
Advanced concepts, such as conditions, actions, timeouts, and composite states will be discussed further in subsequent articles.
我们将在后续文章中讲述一些高级概念，例如条件、操作、超时和组合状态。
The method used for analyzing traces to determine the cause of transaction timeouts can also be used for other types of problems.
用于分析跟踪信息来确定事务超时的原因的方法还可以用于解决其他类型的问题。
All these different manners of defining timeouts must be viewed and handled in concert to achieve the desired end-to-end behavior.
必须协同观察和处理所有这些不同的超时定义方式，以实现所需的端到端行为。
Fault handling should not be part of the model, but left to the workflow developer (for example, the handling of service timeouts).
故障处理不应是模型中的内容，而应留给流程开发人员处理(例如，对服务超时的处理)。
Even with the functionality of lock timeout reporting, it may not always be possible to determine the cause of lock timeouts easily.
即使拥有了锁定超时报告功能，也不是总能够轻松确定出导致锁定超时的原因。
If triggering is not enabled and messages are left unprocessed on queues, there is an increased risk of service failures or timeouts.
如果未启用触发机制且消息在队列上保持未处理状态，那么服务失败或超时的风险将增加。
The work requests can only stay in the queue, postponed for an uncertain length of time, and could potentially hit some timeouts in the meantime.
工作请求只能滞留在队列中，推迟不确定的时间长度，同时可能触及某些超时设置。
If you notice a large number of timeouts or badxids, you could benefit by increasing the timeo parameter with the mount command (details to come).
如果您发现timeouts或者badxids的值很大，那么可以通过使用mount命令增大timeo参数来进行解决(稍后将详细描述)。
When developers embark on a new application, there are a great many configurable Settings they may encounter: timeouts, buffer sizes, and so forth.
当开发人员从事一个新的应用程序时，会碰到很多可配置的设置：超时设定，缓冲区大小，等等。
If you notice a large number of timeouts or badxids, you could benefit by increasing the timeo parameter with the mount command (details to come)..
如果您发现timeouts或者badxids的值很大，那么可以通过使用mount命令增大timeo参数来进行解决(稍后将详细描述)。
It is only when you need to alter timeouts, perform setup operations, or tear down data after a test that you would need to construct a test fixture.
只有在需要更改超时值、执行设置操作或在测试后要拆除数据时，才需要构造一个测试装置。
Two seconds later, as the suspend timeouts expire, the first request is retrieved from the pending queue and resubmitted to the ContinuationServlet.
两秒后，当超过suspend的时限后，将从等待队列中检索第一个请求，并将其重新提交给ContinuationServlet。
Moreover, the inherent flexibility of service-oriented solutions introduces a high level of dynamicity, which is also reflected in how timeouts are handled.
此外，面向服务解决方案固有的灵活性带来了高度的动态性，这也影响了超时的处理方式。
To address this concern, timeouts are typically employed within the business tier to ensure that a process doesn't block beyond a reasonable length of time.
为了打消这个顾虑，通常在业务层中使用超时来确保过程的阻塞不超出合理的时间长度。
In this case, you want to reduce the timeouts that control how long the operating system holds the connections, such as with NDD for Solaris or no for AIX.
在这种情况下，可以考虑减少连接超时值，这些值控制操作系统维持连接多长时间；这可以使用Solaris的ndd或aix的no来设置。
应用推荐