Short timeouts and quick retries.
短时间超时与快速重试。
Set the client page timeouts to 2 minutes or less.
请把客户机页面超时设置为2分钟或更短。
Support for timeouts, fault handling and recovery.
支持超时、失败处理和恢复。
Designing a concurrent blocking queue with timeouts.
设计有超时限制的并发阻塞队列。
Timer guards always correspond to setting (absolute) timeouts.
计时器警卫 总是和设置(绝对)超时对应。
It also needs to keep track of users and connection timeouts.
这种方法也需要记录用户和连接超时。
It is common for semaphore timeouts to occur on a busy server.
在忙碌的服务器上出现信号量超时是很常见的。
Transaction timeouts are another common problem that can occur.
事务超时是另一个经常出现的常见问题。
The pthreads implementation supports both blocking and timeouts.
pthreads 实现既支持阻塞也支持超时。
However, browser and other timeouts could easily break this solution.
然而,浏览器和其他超时设置可以很容易地暂停该解决方案。
A fourth group of timeouts are those set by the client of a request.
第四组超时是由请求的客户端设置的。
The 2.6.22 code averaged 17 timeouts for each run of the test client.
在测试客户的每次运行中,2.6.22 代码平均有 17 次超时。
Timeouts are not on the tasks themselves, but rather on the task node.
超时不是发生在任务自身,而是发生在任务节点上。
The solution must avoid session lock timeouts and long wait for locks.
解决方案必须避免会话锁超时和长时间等待锁。
Fewer timeouts means the sender maintained a larger window on average.
超时更少意味着发送方要保持一个均值更大的窗口。
Note that semaphore timeouts do not always indicate a performance problem.
注意,信号量超时并不一定表示性能问题。
In this example, 430d is the semaphore name, and 58 is the number of timeouts.
在这个例子中,430d是信号量名称,58是超时的数量。
In basketball timeouts provide an opportunity to regroup and substitute players.
篮球赛中的休息给重组队员和替换队员提供了机会。
Transaction timeouts are always indicated by the WTRN0006W message. For example.
事务超时始终由WTRN0006 W消息进行指示。
If timeouts are not expected, then throwing an exception might be a better choice.
如果预料不会超时,则引发异常可能是一种更好的选择。
Between each one of these components you have the potential for timeouts to occur.
在这些组件之间,都有出现超时的可能性。
There are many points in a solution design where timeouts can and should be configured.
在解决方案设计中有多个应配置超时的点。
In some cases, timeouts must be considered as a somewhat common, almost normal occurrence.
在某些情况下,必须将超时视为普遍的,在正常情况下会出现。
Business calendars can then be used for durations or timeouts in WebSphere Process Server.
然后可以将业务日历用于WebSphere Process Server中的持续时间或超时。
This introduces yet even more ways of defining timeouts as part of their higher level function.
这就带来了更多将超时定义为其更高级别的功能的一部分的方法。
A signal thread handles alarms and forces timeouts on connections that have been idle too long.
一个信号线程处理警报并在闲置时间过长的连接上强制执行超时。
Timeouts can serve as a constraint and control the amount of time the worker thread is blocked.
可以使用超时来约束和控制阻塞工作线程的时间量。
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.
上述示例仅仅是触及了超时的表层,展示了所有解决方案中普遍存在的超时。