SA-20333

Summary

Customer is facing issue with MQListener they have created. It is not able to get any message and from SMA the status of the listener is disabled. The Test Connectivity is good for the listener and prConfig for initServices/initMQ is also "true" as shown in the document. On checking the logs observe below error

Couldn't get messages from queue :com.pega.pegarules.pub.services.ResourceUnavailableException: Couldn't get handle to queue 'QLS.ADT.ACK.MSG.QDC.SVC': com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2035'.
com.pega.pegarules.pub.services.ResourceUnavailableException: Couldn't get handle to queue 'QLS.ADT.ACK.MSG.QDC.SVC': com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2035'.

Error Messages

2016-02-26 10:22:34,516 [      MQ-Thread-9893] [  STANDARD] [                    ] (        services.mq.MQListener) ERROR MQ.UrgentResultListener.QLSMQServer ListenerUser -  Caught MQException in listener QLSMQServer.UrgentResultListener
com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2035'.
 at com.ibm.mq.MQDestination.open(MQDestination.java:334)
 at com.ibm.mq.MQQueue.<init>(MQQueue.java:260)
 at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:2750)
 at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:2778)
 at com.pega.pegarules.integration.engine.internal.services.mq.MQListener.initializeConnection(MQListener.java:834)
 at com.pega.pegarules.integration.engine.internal.services.mq.MQListener.run_(MQListener.java:643)
 at com.pega.pegarules.integration.engine.internal.services.listener.ServiceListenerBaseImpl.run(ServiceListenerBaseImpl.java:453)
 at java.lang.Thread.run(Thread.java:745)

Steps to Reproduce

1) For 1st issue, Selected Listener from SMA and started. But is's status is disabled.

2) For 2nd issue,Clicked on message explorer, it is showing queue is not found.

Root Cause

destination queue is not valid. Copied the working instance queue in non-working environment.

Resolution

 

Suggested user to validate the destination queue. It's not the problem with PRPC.