Support Article
JMS Listener does not connect with MQ
SA-8584
Summary
JMS Listener fails to connect to MQ.
The reason is due to JMS Listener setting Client ID and MQ client jar throws error 'java.lang.RuntimeException: This JMSProvides does not support Durable Subscriber.'
Error Messages
2015-04-07 11:08:50,051 [ JMS-Thread-233] [ STANDARD] [ ] ( services.jms.JMSListener) ERROR .- Caught java.lang.RuntimeException in listener
java.lang.RuntimeException: This JMSProvides does not support Durable Subscriber.
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.initializeConnection(JMSListener.java:1081)
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.runPoller(JMSListener.java:764)
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.run_(JMSListener.java:759)
Steps to Reproduce
Configure JMS Listener with 'durable subscriber?'
Root Cause
The root cause of this problem is defect/misconfiguration in the operating environment.
Resolution
Pega 7 calls 'setClientID' on JMS Topic Connection before calling 'start'. You must work with MQ/Application server administrator to make necessary configuration changes.
Set ClientID in JMS Topic connection factory at JBoss application server mentioned as below:
class-name="com.ibm.mq.connector.outbound.ManagedTopicConnectionFactoryImpl" jndi-name="java:/jms/Topic" pool-name="PoolA" >
<config-property name="clientID">s1infpegaapp01-intake</config-property>
</connection-definition>
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.