2053 Mq Error
Contents |
2053 Technote (troubleshooting) Problem(Abstract) MQ Connector fails to write messages to queue or publish to topic. Symptom Job log contains error mq 2053 reason code message similar to this: WebSphere_MQ_Connector,0: MQPUT call executed with completion code 2 reason '2053' ('mqrc_q_full') (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
Mq Error 2035
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
Mq Error 2058
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 mqw102 | 2053 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. Document information More support for: InfoSphere DataStage Software version: 8.0, 8.1, 8.5, 8.7 Operating system(s): AIX, HP-UX, Linux, Solaris, Windows Reference #: 1580423 Modified date: 2012-09-25 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
write messages) : DataStage MQ Connector fails with 2053 Error(Fail to write messages) : DataStage January 19, 2014 Kuntamukkala RaviBoot Camp, DataStage, Known Errors, Parallel Jobs, Server Jobs, Stages Are you using a real-time stages to push few XML's to downstream systems such as MQ connector? Recently I have faced a typical error wherein DataStage job fails with 2053 error most of the times(until the queue is cleared) Job log contains error message similar to this: [box style='error'] MQ_Connect_ETL,0: MQPUT call executed with completion code http://www-01.ibm.com/support/docview.wss?uid=swg21580423 2 (MQCC_FAILED), reason code 2053 (MQRC_Q_FULL) MQ_Connect_ETL,0: [IIS-CONN-WSMQ-000017] Put message failed with reason code: 2053 (MQRC_Q_FULL) (CC_WSMQMessageConsumer::processOneTopLevelDataItem(), file CC_WSMQMessageConsumer.cpp, line 643) [/box] Problem would be due to 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 In order to resolve this http://www.technixgeek.com/mq-connector-fails-with-2053-errorfail-to-write-messages-datastage/ error 1. Ask your consumer to clear the Messages in Target Queue If #1 doesn't work or 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. 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). Thanks Share this:Click to share on Twitter (Opens in new window)Click to share on Facebook (Opens in new window)Click to share on Google+ (Opens in new window)Like this:Like Loading... Related DataStage, ETL, Known Errors, Parallel Jobs, Server Jobs, Stages, Workarounds Author: Kuntamukkala RaviETL Consultant by Profession, Webmaster by Passion Post navigation DataStage job aborts with CLI0106E [Connection is closed] error | [Updated] DataStage job with MQ Connector aborts with error code 2058 (Failed to conn
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support
MQSeries.net Forum Index » IBM MQ API Support » MQPUT returned Reason Code 2053 but Q not full MQPUT returned Reason Code 2053 but Q not full « View previous topic :: View next topic » Author Message Strevo Posted: Wed May 10, 2006 5:53 am Post subject: MQPUT returned Reason Code 2053 mq error but Q not full NewbieJoined: 10 May 2006Posts: 3Location: Glasgow Using MQSeries on Tandem NonStop Kernel I'm being returned Reason Code 2053 although the Q is only 5% full. I'm buffering up multiple PUT's into one TMF TRansaction, however I'm being returned Q Full. Can anybody out there help at all? Cheers, John_________________Crystal Palace - Pride of London Back to top wschutz Posted: Wed May 2053 mq error 10, 2006 6:40 am Post subject: Jedi KnightJoined: 02 Jun 2005Posts: 3316Location: IBM (retired) Might you have uncommitted messages on the queue?_________________-wayne Back to top Strevo Posted: Wed May 10, 2006 6:46 am Post subject: NewbieJoined: 10 May 2006Posts: 3Location: Glasgow wschutz wrote: Might you have uncommitted messages on the queue? I do have, but nowhere near enough to make it full. It has a maximum Q depth of 50000 messages, and I'm only gathering up 500 at a maximum before committing (with a current total 1500 msgs on the Q). I've even tried bringing the batch volume down to a maximum of 10 instead of 500 but still the same problem._________________Crystal Palace - Pride of London Back to top AndyMQ Posted: Wed May 10, 2006 8:43 am Post subject: ApprenticeJoined: 22 Apr 2004Posts: 33Location: Scotland Strevo, have you checked the physical file? If you run a dspmqfls and find the actual underlying queue and overflow file names and check you haven't hit maxextents Back to top Strevo Posted: Thu May 11, 2006 3:53 am Post subject: NewbieJoined: 10 May 2006Posts: 3Location: Glasgow Thanks for your help guys, problem now solved,