It also provides for a work-queue based working style, where an administrator can transfer work items among groups.
它还提供了基于工作队列的工作方式，在这种方式中，管理员可以在组之间转移工作项目。
In the previous section, you configured a shared work path and set up an MI queue manager, so you can move on to third step.
在上一节中，您配置了一个共享工作路径并设置了一个MI队列管理器，因此您可以继续第三步。
A key problem with this model is that increasing the number of worker threads increases the contention on the work queue (this is shown in Figure 3).
对于该模型的一个关键问题是增加工作线程数会加剧对工作队列的争用(如图3所示)。
Listing 1 shows an example of a simple pooled work queue.
清单1显示了简单的合用工作队列的示例。
Suppose we wanted to add Business Process management (BPM) to the solution, such that when the message came in, it is stored in some sort of work queue for an editor to approve.
假设我们想在解决方案中添加业务流程管理(BPM)，比如在消息传入时，以某种工作队列的分类存储该消息，以便编辑器进行核准。
All the servant regions are now bound to existing work queues, and no servant region can immediately convert to the new service class work queue.
现在所有服务区域均绑定到现有工作队列，没有任何服务区域能够立即转换到新的服务分类工作队列。
Basically, at any given time, any servant region will only bind to a single specific service class work queue and select requests from there.
本质上，在任何给定的时间，任何服务区域将仅绑定到单个特定的服务分类工作队列，并从该队列选择请求。
The following example illustrates a few of the core work queue API functions.
下面的例子说明了几个核心的工作队列api函数。
The work queue mechanism is inherited from the WLM queuing manager service.
工作队列机制是从wlm队列管理器服务继承而来的。
The Activities act like a work queue, where work is assigned and completed.
这些活动像一个工作队列，工作在这里被分配和完成。
In the panel shown in Figure 11, there are two servant regions bound to the same service class work queue, CBDEF.
在如图11所示的面板中，有两个服务区域与同一个服务分类工作队列CBDEF绑定。
The optimum size of a thread pool depends on the number of processors available and the nature of the tasks on the work queue.
线程池的最佳大小取决于可用处理器的数目以及工作队列中的任务的性质。
These functions (shown in Listing 8) mimic those from Listing 7, except that you don't need to define the work queue structure.
这些函数(见清单8)模拟清单7，只是不需要定义工作队列结构体。
A new request comes in and stays in the new service class work queue.
新的请求传入并滞留在新的服务分类工作队列中。
That's the core of the work queue API.
这就是工作队列api的核心。
The following class is a model of a common concurrent utility: a work queue.
下面的类是一种常见的并行实用程序模型：任务队列。
Let's now continue with a simple example of the work queue API.
下面我们看一个工作队列api的简单例子。
Before the request is processed by the servant region, it's put inside the WLM work queue.
在服务区域处理请求之前，请求被放在WLM工作队列中。
The work queue API provides three functions to initialize work (from an allocated buffer); see Listing 6.
工作队列API提供三个函数来初始化任务（通过一个事先分配的缓存）；参见清单6。
Work queue and servant region relationship
工作队列与服务区域的关系
The administration work queue lets you see the list of administration actions queued up on a broker that are waiting to be actioned
管理工作队列使您可以查看在一个等待行动的代理上排队等候的管理活动的列表
For the former, the Gearman work queue remains in memory but is backed by a relational database.
对于前者，Gearman工作队列保存在内存并在一个关系型数据库内存有备份。
Finally, Query also includes the option to constrain a search to a particular container (folder or work queue).
最后，Query还包含将搜索限制在特定容器(文件夹或工作队列)的选项。
The column WUQue reports only the number of requests taken from the service class work queue that are bound to the server region.
WUQue列仅报告从服务分类工作队列接收并绑定到该服务区域的请求数量。
What we usually want is a work queue combined with a fixed group of worker threads, which USES wait and notify to signal waiting threads that new work has arrived.
我们通常想要的是同一组固定的工作线程相结合的工作队列，它使用wait和notify来通知等待线程新的工作已经到达了。
WebSphere Application Server for z/OS combines a work queue mechanism with the thread pool to serve the client requests.
WebSphereApplicationServerfor z/OS 将工作队列机制与线程池组合起来为客户端请求提供服务。
Thus, if the Gearman daemon fails, it can recreate the work queue on restart.
这样一来，如果Gearman守护程序故障，它就可以在重启后重新创建这个工作队列。
WUQue is the total number of requests taken from the work queue.
WUQue是从工作队列接收的请求总数。
WUQue is the total number of requests taken from the work queue.
WUQue是从工作队列接收的请求总数。
应用推荐