Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Issue with Message Explorer in MQ Listener

SA-20247

Summary



An error appears when Message Explorer in MQ Properties of MQ Listener is clicked.

Error Messages



Couldn't find the queue 'QLS.ADT.ACK.MSG.QDC.SVC', Please run test connectivity.
Error Details : com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2035'.

Steps to Reproduce



Click Message Explorer in the MQ properties tab of Listener.

Root Cause



A defect or configuration issue in the operating environment:
The root cause of this problem is due to strict permissions in the Pega Connect-MQ logic.

Resolution



Perform the following local-changes:

1. Check with the MQ Administrator if there is “com.ibm.mq.MQC.MQOO_SET_IDENTITY_CONTEXT” MQOPEN OPTIONS set for the queues. If yes, remove this option.
2. Override invokemqconnector activity to the local ruleset.

     In invokeMQConnector activity, which is one java step, change the line given below:

     int reqQueueOpt = com.ibm.mq.MQC.MQOO_OUTPUT | com.ibm.mq.MQC.MQOO_SET_IDENTITY_CONTEXT;

     to:
     int reqQueueOpt = com.ibm.mq.MQC.MQOO_OUTPUT;

    Save, and check in invokemqconnector activity.

3. Save the activity validateInfrastructureConnectMQ to custom ruleset with similar changes.

    In step 3 of the activity, change the line given below:

   int reqQueueOpt = com.ibm.mq.MQC.MQOO_OUTPUT | com.ibm.mq.MQC.MQOO_SET_IDENTITY_CONTEXT;

   to:
   int reqQueueOpt = com.ibm.mq.MQC.MQOO_OUTPUT;

   Save and check in validateInfrastructureConnectMQ activity.

Published March 1, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us