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

JMS Listener does not connect with MQ



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. 

Steps to Reproduce

Configure JMS Listener with 'durable subscriber?'

Root Cause

The root cause of this problem is defect/misconfiguration in the operating environment.


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="" jndi-name="java:/jms/Topic" pool-name="PoolA" >
<config-property name="clientID">s1infpegaapp01-intake</config-property>

Published January 31, 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