Immediately check that messages are now queued on DCQ1 on QM2.
立即检查，看看消息现在是否在QM 2上的DCQ1中排队。
Similarly, the queue manager QM2 has the following WebSphere MQ objects.
同样地，队列管理器QM2也具有以下WebSphereMQ对象。
Therefore messages put by the application connected to QM1 will not be sent to QM2, and hence, all messages will be sent to QM3.
因此，由连接到QM1 的应用程序放置的消息将不会被发送到QM2，这样，所有消息都将被发送到QM3。
Using Figure 1 above as an example, if CLUSQ1 on QM2 is altered to be put-disabled, the object change is automatically propagated to QM1.
以上面的图1为例，如果QM 2上的CLUSQ1更改为禁用放置，则对象变更被自动传播到QM1。
By default, clustering load balances messages equally between the instances of CLUSQ1 on QM2 and QM3, even though CLUSQ1 on QM3 is not being served by a message consumer application.
默认情况下，集群机制在QM2和QM 3上的CLUSQ1的各个实例之间均等地平衡消息负载，即使一个消息使用方应用程序当时不对QM 3上的CLUSQ1提供服务。
In this situation, whilst the application server is offline, it is better to send all messages to CLUSQ1 on QM2, which has an active application server and message consumer application.
在这种情况下，当该应用程序服务器离线时，最好将所有消息发送到拥有一个活动应用程序服务器和消息使用方应用程序的QM 2上的CLUSQ1中。
In this situation, whilst the application server is offline, it is better to send all messages to CLUSQ1 on QM2, which has an active application server and message consumer application.
在这种情况下，当该应用程序服务器离线时，最好将所有消息发送到拥有一个活动应用程序服务器和消息使用方应用程序的QM 2上的CLUSQ1中。
应用推荐