工作请求进入队列，等待工作线程。
Work requests queued and waited for a worker thread to become available.
工作线程循环等待新请求。
阻塞工作线程并等待响应。
可运行线程在J2EE工作线程上运行。
将请求分配给新工作线程。
创建足够的工作线程以实现最佳吞吐量。
工作线程现在等待更多工作出现在输入队列上。
The worker thread now waits for more work to appear on the input queue.
恢复阻塞工作线程。
当完成时，J2EE工作线程仍保持活动状态。
工作线程的数量与Web客户机的数量无关。
The number of worker threads is independent of the number of Web clients.
可以使用超时来约束和控制阻塞工作线程的时间量。
Timeouts can serve as a constraint and control the amount of time the worker thread is blocked.
工作线程从输入队列提取一个WWEC，并运行它。
A worker thread pulls the next WWEC from the input queue and runs it.
队列模型能够帮助标识soa中阻塞工作线程的影响。
Queuing models can help identify the effects of blocking worker threads in an SOA.
正如前面提到的，单个工作线程无法并行处理多个事务。
As previously stated, a single worker thread can't process multiple transactions in parallel.
J2EE工作线程现在等待更多工作出现在输入队列上。
The J2EE worker thread now waits for more work to appear on the input queue.
通过更改工作负载概要调整每个服务区域的工作线程数量。
Adjust number of worker threads for each servant region by changing the workload profile.
对银行设备的每次服务调用都会阻塞服务器内的工作线程。
Each service invocation to the banking device blocks a worker thread within the server.
线程池工作线程从输入队列提取下一个WWEC，并运行它。
A thread pool worker thread pulls the next WWEC from the input queue and runs it.
如果阻塞工作线程，则需要确保仅在合理的时间内阻塞线程。
If a worker thread must be blocked, you need to ensure that the thread is blocked for only a reasonable amount of time.
在工作线程完成其事务后，将会执行队列中的下一个工作项目。
As the worker threads complete their transactions, the next work item in the queue is executed.
为了处理(消费)队列中的请求，生成了不定数量的工作线程。
A variable number of worker threads are spawned to process (consume) requests off the queue.
工作线程的数量是CPU数量的三倍，但是不小于5和不大于30。
The number of worker threads is three times your number of CPUs, but it's no less than 5 and no larger than 30.
每个工作线程都有适用于它的线程池创建程序组件的J2EE上下文。
Each worker thread has the J2EE context of the thread pool creator component applied to it.
因此不允许从工作线程中操作ui——只能从UI线程中操作用户界面。
So, you must not manipulate your UI from a worker thread-you must do all manipulation to your user interface from the UI thread.
当请求的数量增加，并且工作线程的数量太少时，处理请求则需要很长时间。
When the number of requests increases and the number of worker threads is too small, it may take a long time for requests to be processed.
如果应用程序结束，将调用池中每个守护程序工作线程的release方法。
If the application ends, the release method of each daemon Work thread in the pool will be called.
如何选择正确的工作负载概要并设置恰当的工作线程数量才能实现最佳的吞吐量呢？
How do you choose the right workload profile and set the proper number of worker threads to achieve the best throughput?
很多工作线程可能会突然阻塞，并等待超时过期，不过同时又有新工作送到服务器。
Many worker threads can suddenly block and wait for some timeout to expire; in the meantime however, new work arrives to the server.
您只需设置用于工作负载执行的适当工作线程数量，而不必考虑客户端请求的数量。
You only need to set a proper number of worker threads for workload execution, without having to consider the number of client requests.
获取工作线程上当前J2EE应用程序上下文的快照，以便在工作完成之后进行恢复。
A snapshot is taken of the current J2EE application context on the worker thread to restore later after the work completes.
应用推荐