Support Article
Connect-MQ error-com.ibm.mq.MQException: MQJE001
SA-6671
Summary
When posting message to MQ using Connect-MQ method, user gets an error after the execution. Although they are able to put message successfully, the error is hindering the further processing. They want a mechanism to push a message to MQ asynchronously.
Error:
couldn't get message from queue 'HSIC.PEGA.IN.CTWLOANACTIVITYLIST': com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2033'.
Error Messages
couldn't get message from queue 'HSIC.PEGA.IN.CTWLOANACTIVITYLIST': com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2033'.
Steps to Reproduce
1. Call Connect-MQ method in activity
Root Cause
The root cause of this problem is that Websphere MQ has not been configured for synchronous messaging. This is causing PRPC to fail with the ERROR above because Out-of-the-box InvokeMQConnector activity is designed for synchronous message puts and expects a REPORT/REPLY message in a configured Response queue.
Resolution
This issue is resolved through the following local change:
As user’s application requirement is not to have synchronous messaging PUTs (in other words to listen for MQ delivery replies/report messages in the response queue), we have overridden the Out-of-the-box InvokeMQConnector activity to ignore the response message handling and wait.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.