Troubleshooting
Problem
MQ Connector fails to write messages to queue or publish to topic.
Symptom
Job log contains error message similar to this:
WebSphere_MQ_Connector,0: MQPUT call executed with completion code 2 (MQCC_FAILED), reason code 2053 (MQRC_Q_FULL)
WebSphere_MQ_Connector,0: [IIS-CONN-WSMQ-000017] Put message failed with reason code: 2053 (MQRC_Q_FULL) (CC_WSMQMessageConsumer::processOneTopLevelDataItem(), file CC_WSMQMessageConsumer.cpp, line 643)
Cause
There are typically two reasons for this error:
1) maximum queue depth (MAXDEPTH) has been reached.
2) maximum number of un-commited messages (MAXUMSGS) for the queue manager has been exceeded
Diagnosing The Problem
One must look into the MQ queue manager and specific queue properties to determine what is the reason for the MQ 2053 error. If the current depth (CURDEPTH) is close to maximum queue depth (MAXDEPTH) then removing messages from the queue or increasing the maximum queue depth can resolve the issue.
If the queue depth is not the issue then the issue can be caused by a large transaction of messages being written to the queue with single commit at the end of the transaction. In MQ Connector there is Transaction - record size setting that controls how many messages are written in a single transaction (default value is 0 = all messages are committed at the end). If there is large number of messages participating in a single transaction, the queue manager's maximum number of uncommitted messages can be reach (the limit is queue manager specific so all active transactions count towards this limit). If the MAXUMSGS is the issue, one can set lower record count for the transaction in MQ Connector to force MQ Connector to commit fewer messages per transaction.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21580423