ibm-mq - WebSphere MQ 中的 MQRC 资源问题

Question

这是在集群环境中。队列管理器在集群中丢失了身份，无法连接到其他服务器。存储库和其他 channel 的所有 channel 都在重试状态。

此服务器的 CPU 使用率最佳。这是一个 UNIX 盒子。

当我检查下面的日志时，

AMQ9532: Program cannot set queue attributes.

EXPLANATION: The attempt to set the attributes of queue 'SYSTEM.CLUSTER.TRANSMIT.QUEUE' on queue manager 'QMGR.SERVER6A' failed with reason code 2102.

ACTION: Ensure that the queue is available and retry the operation.

----- amqrmssa.c : 690 --------------------------------------------------------
AMQ9999: Channel program ended abnormally.

EXPLANATION: Channel program 'Channel.Coord00' ended abnormally.

ACTION: Look at previous error messages for channel program 'Channel.Coord00' in the error files to determine the cause of the failure.

----- amqrccca.c : 883 --------------------------------------------------------
03/06/11 08:24:26 AMQ9544: Messages not put to destination queue.

EXPLANATION: During the processing of channel 'Channel.Server6A' one or more messages could not be put to the destination queue and attempts were made to put them to a dead-letter queue. The location of the queue is 1, where 1 is the local dead-letter queue and 2 is the remote dead-letter queue.

ACTION: Examine the contents of the dead-letter queue. Each message is contained in a structure that describes why the message was put to the queue, and to where it was originally addressed. Also look at previous error messages to see if the attempt to put messages to a dead-letter queue failed. The program identifier (PID) of the processing program was '1372200'.

----- amqrmrca.c : 1318 -------------------------------------------------------

那我确实回收了队列管理器，现在可以了吗？

我这里的问题是MQ资源问题是怎么发生的？此服务器的 CPU 使用率不超过 15%。请指教。

Answer 1

日志中显示了三个不同且不相关的问题。

AMQ9532: Program cannot set queue attributes.

EXPLANATION: The attempt to set the attributes of queue 'SYSTEM.CLUSTER.TRANSMIT.QUEUE' on queue manager 'QMGR.SERVER6A' failed with reason code 2102.

2102 是 MQRC_RESOURCE_PROBLEM，大概是帖子中提到的资源问题。 2102 可以是任何类型的稀缺资源，包括信号量、用户进程、队列句柄等。由于 QMgr 试图设置队列的属性，因此它已经实例化了一个线程，但它需要额外的队列句柄.发生此类情况时，请使用您的管理工具(WMQ Explorer、mqmon 或众多 3rd 方工具之一)查看打开队列句柄、打开 channel 等的数量。请注意，对于资源错误，这是必要的保持与 QMgr 的开放连接，否则该工具将无法在发生资源短缺时建立新连接。

AMQ9999: Channel program ended abnormally.

EXPLANATION: Channel program 'Channel.Coord00' ended abnormally.

ACTION: Look at previous error messages for channel program 'C00.US.MP00' in the error files to determine the cause of the failure.

这个错误实际上是两个不同的错误，因为它引用了两个不同的 channel 。其中一个似乎是出站集群 channel ，另一个似乎是点对点 channel 。此错误中提到的 channel 都与第一条和最后一条错误消息无关。

03/06/11 08:24:26 AMQ9544: Messages not put to destination queue.

EXPLANATION: During the processing of channel 'Channel.Server6A' one or more messages could not be put to the destination queue and attempts were made to put them to a dead-letter queue. The location of the queue is 1, where 1 is the local dead-letter queue and 2 is the remote dead-letter queue.

ACTION: Examine the contents of the dead-letter queue. Each message is contained in a structure that describes why the message was put to the queue, and to where it was originally addressed. Also look at previous error messages to see if the attempt to put messages to a dead-letter queue failed. The program identifier (PID) of the processing program was '1372200'.

最后一个错误似乎是入站集群 channel 。由于第一个错误是尝试设置集群传输队列的属性，因此它只能与出站 channel 相关联。因此，第一个和最后一个错误消息是不相关的。此错误消息似乎显示了一个发往队列的入站消息，并且该队列已满、已禁用 PUT 或无法接受该消息。因此，消息被路由到死信队列。

对于资源错误，我建议您查看适合您平台的性能报告。转至 SupportPacs page并查找名为 MP* 的 SupportPac，然后查找适合您平台的 SupportPac。性能报告为您提供了具体的调优建议。

您可能还想查看 Problem Determination有关如何识别资源问题的其他建议，请参阅系统管理手册中的一章。

WebSphere MQ cluster design and operation developerWorks Mission:Messaging 系列中的文章提供了有关保持集群健康的具体建议。

最后但并非最不重要的是， WebSphere MQ MustGather页面包含有关所有主要平台的故障排除部分，并按问题区域分类。