Mq Error Reason 2053
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 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 http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.tro.doc/q041240_.htm 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 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 http://www.technixgeek.com/mq-connector-fails-with-2053-errorfail-to-write-messages-datastage/ 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 connect to Queue Manager) Leave a Reply Cancel reply Your email address will not be published. Required fields are marked * Name * Email * Website Comment Notify me of follow-up comments by email. Notify me of new posts by email. Archives August 2015 January 2015 August 2014 July 2014 May 2014 January 2014 December 2013 November 2013 Home BI & DW DataStage Boot Camp Known Errors Information Server Stages Parallel Jobs Server Jobs ETL Contact us ©201
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss http://stackoverflow.com/questions/26481840/queuesender-send-when-reach-max-q-depth the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each mq error other. Join them; it only takes a minute: Sign up queueSender.send when reach max q depth up vote 0 down vote favorite I am using queueSender.send(msg) to send the message to destination q. Here q session is not transactional and queueSender's delivery mode is default mode [i believe default is PERSISTENT]. What will happend if application is still mq error reason sending message when the q has reached the max q depth. Is there any issue with the app performance? What is the best way to handle this? mq share|improve this question asked Oct 21 '14 at 8:11 user3279624 64 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote Performance turn the receiving application to make sure it keeps up with the message flow. Increase the receiving application's queue from a default depth of 5000 to 200000 (or some really large value) Make sure the sending application can handle a reason code of 2053 (MQRC_Q_FULL). i.e. pause the application or put the messages to another queue. Updated: If you are using JMS when you put a message to a full queue, you will get a JMS exception: JMSWMQ2007. If the JMSException is not null then get the LinkedException. i.e. catch (JMSException e) { System.err.println(e.getLocalizedMessage()); if (e != null) System.err.println("getLinkedException()=" + e.getLinkedException()); } And the error messages should look like: JMSWMQ2007: Failed to send a message to destination 'TEST.Q25'. getLinkedException()=c