With run time for most applications lasting days or weeks, the queue fills up quickly.
由于大多数应用程序的运行时间要持续数天或数周，队列很快就满了。
Applications using the MQ server can send messages that are destined for device queue managers.
使用MQ服务器的应用程序可以发送去往设备队列管理器的消息。
Target applications can then subscribe to the queue and obtain the message using either the read or receive function.
然后，目标应用程序可以订阅这个队列，并使用读取或接收函数获得消息。
The basic functions of a custom event handler are to consume the event messages in the JMS queue and interact with external applications accordingly.
一个定制的事件处理器的基本功能是使用jms队列中的事件消息，然后相应地与外部应用进行交互。
It is worth stressing that, unless you require backwards compatibility, there is no reason to write new JMS applications using the old queue and topic interfaces.
值得强调的是，除非需要向后兼容性，否则没有理由用老的队列和主题接口编写新的JMS应用程序。
You can avoid these outages by defining the queue on other queue managers in the cluster, so that whilst migrating one queue manager, applications can use the alternate queues.
要避免这种中断，可以在该集群内的另一个队列管理器上定义该队列，这样，当您迁移一个队列管理器时，应用程序就可以使用备用队列。
If the queue manager is ever restored from the backup, the impact to all those applications is unpredictable at best.
万一要从备份中恢复队列管理器，对所有那些应用程序的影响在最好的情况下也是不可预测的。
Applications and broker queue manager are located on the same system.
应用程序和代理队列管理器位于同一系统中。
As noted earlier, users are coming out from behind server applications and connecting to the queue manager directly.
前面提到过，用户从服务器应用程序后面出来并直接连接到队列管理器。
The solution USES a simple application to get each message from the cluster queue with no active message consumer applications and put them to another cluster queue.
这个解决方案使用一个简单的应用程序从没有活动消息使用方应用程序的集群队列提取消息，并将它们放置到另一个集群队列中。
In addition, applications connected to the partial repository queue managers need to put messages to clustered queues which might be hosted on some other node.
此外，连接到部分储存库队列管理器的应用程序需要将消息放到集群队列中，集群队列可能驻留在其他节点上。
When these hard limits are reached, the entire queue manager and all connected applications come to a halt.
当达到这些硬限制时，整个队列管理器和所有已连接的应用程序都将停顿下来。
Have the injector applications connect (using bindings) to a local queue manager and use MQ networking to move the messages onto the test system.
将注入器应用程序连接(使用绑定)到本地队列管理器，并且使用MQ网络将消息移到测试系统中。
It is possible to have tens or hundreds of applications running concurrently without any detrimental impact on queue manager log performance.
完全可能让数十或数百个应用程序并发执行，而不会对队列管理器日志性能造成任何负面影响。
After a queue manager has been migrated, you should verify existing function and applications.
迁移队列管理器后，应该验证现有功能和应用程序。
It is reasonable to leave days between migrating each queue manager in the cluster, in order to test applications before wholly committing all queue managers to run at the new version.
在迁移集群中的各个队列管理器之间最好间隔几天，以便在所有队列管理器完全在新版本下运行之前测试应用程序。
A message is simply a string of bytes that is meaningful to the applications that use it, and a queue is a container for messages.
一条消息仅是对使用它的应用程序有意义的一串字节，而队列则是消息的容器。
Using multiple queues in this manner does not help if applications have affinities with a particular queue.
但是如果应用程序与某个特定队列具有亲和性，那么以这种方式使用多个队列也没有用。
Publishing and subscribing to a queue is an effective configuration for exchanging information between multiple applications on multiple subjects.
对一个队列的发布和订阅，对于在多个应用程序之间基于不同主题交换信息来说是一种有效的配置。
Applications that get messages from the dead-letter queue must verify that the messages begin with an MQDLH structure.
从死信队列获取消息的应用程序必须确保消息以MQDLH结构开头。
When a queue manager is configured as the default queue manager, applications can access it without knowing its name.
将队列管理器配置为缺省队列管理器时，应用程序可以在不知道其名称的情况下对其进行访问。
Ideally, the cluster queue manager will also be tested before bringing applications back online.
理想情况下，集群队列管理器在使应用程序重新上线前也将被测试。
Messages can be put on the dead-letter queue by queue managers, message channel agents (MCAs), and applications.
消息可由队列管理器、消息通道、消息通道代理程序(mca)和应用程序放到死信队列上。
Applications connect to a queue manager which is remote from the broker queue manager.
应用程序连接到(相对代理队列管理器来说)远程的队列管理器。
Automatic reconnect for JMS applications to a standby gateway queue manager when an active queue manager fails or becomes unavailable.
当某个活动队列管理器失败或变得不可用时，JMS应用程序会自动重新连接到备用网关队列管理器。
The trick is in how you authenticate remotely connected users, applications connecting in client mode, and connections from other queue managers.
问题在于，您如何对远程连接用户、以客户端模式连接的应用程序以及来自其他队列管理器的连接进行身份验证。
In addition, while that log write is taking place access to the queue is inhibited for other applications.
此外，在进行日志写入时，队列无法供其他应用程序使用。
The active queue manager instance processes messages and accepts connections from applications and other queue managers.
激活的队列管理器实例可以处理信息并接受来自应用程序和其他队列管理器的连接。
Stop the queue manager and any associated applications.
停止队列管理器和任何关联的应用程序。
Simplicity of infrastructure means the applications must establish, for example, message formats and queue attributes.
由于基础设施的简单性，应用程序必须自行处理一些事情，例如建立消息格式和队列属性。
应用推荐