我看到一个场景，当应用程序将消息发送到同一服务器上的主题时，消息会卡在传输队列中，直到我启动通道或将测试消息（使用“amqsput”）放到队列管理器中消息必须去。在此通道启动或处于运行状态后，放入主题的消息将正常流动。在没有通道运行的几个小时或一天之后，当应用程序将一条消息放到主题中时，它再次卡在传输队列中，直到我执行上述练习。
这是在集群环境中。 MQv7.0.1.6
为什么即使远程 MQ 运行良好，消息也必须停留在 trasnmit 队列中？只有当应用程序向主题发布消息时才会出现这种情况。
【问题讨论】：
标签： ibm-mq
2014 年 1 月 23 日更新
IBM 已回复我的 PMR 作为 IV21703: A WMQ V7 CLUSSDR CHANNEL IS NOT STARTED WHEN PERSISTENT PUB/SUB MESSAGES ARE PUT TO CLUSTERED TOPICS 的匹配项。
错误描述
When messages are put to cluster queues in syncpoint the cluster
channels are not started until the application calls MQCMIT;
the CLUSSDR channels to all the queue managers which are
destinations for messages put in the Unit of Work are started
during commit processing.
This operation does not appear to be carried out when
publications are put to remote cluster subscriber queues at the
commit of the internal Unit of Work, that is, the cluster
channels associated with the put of the subscriber messages are
not started at that time. The channels are held in the queue
manager's memory associated with the connection, and are
started when the application is disconnected and the connection
is closed.
本地修复
There are 4-
1. Change PMSGDLV to ALLAVAIL
2. Change the messages to non-persistent
3. Change the CLUSRCVR channels to DISCINT(0)
4. Call MQDISC after putting msgs to a clustered topic
在 7.0.1.10 和 7.1.0.2 中进行了修复，但 APAR 中未提及 7.5。临时修复适用于 7.5.0.0 及更高版本。它的目标是包含在 1Q14 的 FP7.5.0.3 中。
之前基于集群名称解析的答案被证明是完全错误的。这是一个可行的理论，但仍然是错误的。我已经删除了。
【讨论】：