为了保持队列深度值较低，服务器进程必须以更高的速率运行。
To keep the queue depth low, the server process would have to run at a higher rate.
回撤流程可能包括从集群移除或挂起队列管理器、向后迁移和在外部问题得到解决之前保持队列管理器离线。
The procedure could involve removing or suspending the queue manager from the cluster, backwards migrating, or keeping the queue manager offline until an external issue is resolved.
如果您将要重用连接和队列，则应将它们保持打开，而不是重复地打开和关闭、连接和断开连接。
Keep connections and queues open if you are going to reuse them instead of repeatedly opening and closing, connecting and disconnecting.
提示：保持持有队列为空。
主要的区别在于，在该事件之后，将创建过程以确保队列管理器的所有实例保持同步，并将应用于一个实例的更改应用于所有的实例。
The main difference is that after the event, procedures are created to ensure that all instances of the queue manager remain in sync, and changes applied to one are applied to all.
其中的一种方法是保持一个中央队列，并在事件发生时使用它来发送所有通知。
One option is to keep a central queue and use it once to deliver all notifications when an event arises.
在我们给出的简单示例中，由于服务器进程是一个CICS事务，直接在多个CICS区域中运行多个服务器事务副本就可能将队列深度保持在很低的水平。
In our simple example, since the server process is a CICS transaction, simply having multiple copies of the server transaction running in multiple CICS regions would keep the queue depth very low.
将队列管理器名称保持简短，不要超过8个字符。
如果未启用触发机制且消息在队列上保持未处理状态，那么服务失败或超时的风险将增加。
If triggering is not enabled and messages are left unprocessed on queues, there is an increased risk of service failures or timeouts.
消息头保持纯文本格式，以便队列管理器能够正确路由它。
The message header remains in plain text so that the queue manager can route it properly.
当队列管理器使用新值重新启动时，现有队列将保持其之前的定义，而新队列将使用当前参数值创建。
When the queue manager is restarted with new values, existing queues will keep their earlier definitions and new queues will be created with the current parameter values.
如果编码不正确，那么可能丢失通知，导致线程保持空闲状态，尽管队列中有工作要处理。
If coded incorrectly, it is possible for notifications to be lost, resulting in threads remaining in an idle state even though there is work in the queue to be processed.
保持较高的消息处理速率，无论消息类型如何，都尽量减少队列上的消息的数量。
Keep the message processing rate at a high volume so that the number of messages on queue are minimal irrespective of the type of the messages.
为保持文件一致性，我们设计了一个队列，用于放置请求，并按照先到先服务的原则。
To implement file consistency, we have designed a queue that is used to place the request using first-come-first-served basis.
假设您的WebSphereApplicationServer正在保持最大服务区域数量，这些服务区域全都绑定到不同的服务分类工作队列。
Let's assume your WebSphere Application Server is maintaining the maximum number of servant regions, all bound to different service class work queues.
但是发生该异常之后并没有将响应发送给客户机，请求被放到处于等待状态的Continuation队列中，而HTTP连接仍然保持打开状态。
But instead of sending any response to the client as a result of the exception, the request is held in a queue of pending Continuations, and the HTTP connection is kept open.
如果找不到任何结果，队列管理器会在保持ReplyToQ不变的情况下在消息描述符的replytoqmgr字段中置入自己的名称。
If none is found, the queue manager places its own name in the ReplyToQMgr field of the message descriptor, with ReplyToQ unchanged.
保持阻塞状态，直到处理了队列中的所有项目为止。
Blocks until all items in the queue have been gotten and processed.
通过onClose处理、连接保持、消息队列、超时和重试，我们最终实现了一个可以在用户停留在网页上的时候保持其存在状态的聊天室。
With onClose handling, keep-alives, message queues, timeouts and retries, we finally will have a chat room that can maintain a users presence while they remain on the web page.
满足了在发生故障时让系统保持其初始状态的要求，并按照要求初始消息不在WebSphereMQ队列中。
The requirement of having the systems in their original state in case of a failure is satisfied, and the original message is kept aside in a WebSphere MQ queue as per the requirements.
通过利用点对点队列，以及通过MQ使是事件流负荷从入站边保持平衡，可以确保没有复制事件被BusinessEvents接受。
Through the use of point-to-point queues and having the event stream load balanced by MQ from the inbound side, you can ensure that there are no duplicate events being received by Business Events.
这使得邮件信件保持在队列里面，并且，寄希望于使问题被纠正，而不弹回任何信件。
That should cause the mail message to remain in the queue, and, hopefully allow the problem to be corrected, without bouncing any mail.
在模块清理过程中，会清理一些特别的工作队列(它们将保持阻塞状态直到处理程序完成对任务的处理)，然后销毁工作队列。
Here, in module cleanup, you flush the particular work queue (which blocks until the handler has completed processing of the work), and then destroy the work queue.
这样做了以后，要使优先级队列中在任意时刻只保持一条从树中顶点到某边缘点的边就变得容易了。
As it turns out, it is easier to keep only one edge from the tree to a given fringe vertex in the priority queue at any given time.
这个命令配置传输队列并跨越桥接保持信道的同步。
This command configures the transmission queues and keeps the channels synchronized across the bridge.
该队列保持数据包的最大数量，默认是50。（这句看不懂）
The maximum number of packets held in the queue. The default is 50.
通过仿真研究表明，自适应控制器能够很好的进行参数调整，并且使网络系统的队列长度保持在平衡点附近。
During the simulation, the adaptive controller parameters can be adjusted well and the queue length of network system can be maintained at equilibrium point.
AQM通过保持系统的队列长度在稳定的范围内，提高路由器中的数据包利用率并且降低系统的排队延时，改善网络性能，提高网络质量。
AQM queue length by maintaining the system in a stable context, raise the router packet queue utilization and reduce system latency and improve network performance, increase network quality.
跟着“出口”标志走，大家保持冷静，请排成一个队列疏散。
Follow the exit sign and everybody stay calm and in a single file please.
同时对移动机器人队列的路径规划进行讨论，使移动机器人队列在保持队形的前提下顺利到达目标位置。
More, the path planning of multi-robot is provided, the robots of formation system can reach destination smoothly with the right formation.
应用推荐