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 MDB Listener behavior incorrect

SA-2316

Summary



In a multi-node Production environment, user has enabled JMS MDB listener only on one node. JMS messages were being queued to PRPC from an external system. MDB listener was processing the messages intermittently (Response Queue) and remaining messages were routed to Backout Queue. User do not see any errors or exceptions in the PegaRULES log file, System.out file in the current PRPC node.

Error Messages



Following exception traces were observed in other PRPC node(s) -

2014-09-30 22:54:47,591 [AResourceAdapter : 0] [ STANDARD] [ ] (tener.ListenerStateManagerImpl) ERROR - Failed to create MDB Listener, could not find Listener definition for Data-Admin-Connect-JMSMDBListener:MRIAcknowledgment.(com.pega.pegarules.integration.engine.internal.services.jms.JMSListener)
com.pega.pegarules.pub.PRException: Listener is not enabled for node: livlpscimw7
From: (AEDAAEA95819B0A778E622ED67DD319B7)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.getListenerPage(ListenerStateManagerImpl.java:1633)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl$7.run(ListenerStateManagerImpl.java:1078)



Steps to Reproduce


1. Create JMS MDB Listener, which process the messages from MQ.
2. Deploy the EAR with required config changes on all the nodes.
3. In a multi-node environment, enable JMS MDB Listener and run on one node.

Root Cause



Common application EAR file was deployed on all the nodes and hence the other nodes were trying to process the JMS messages. This was an expected behaviour of JMS MQ - when same EAR file was deployed across all the nodes, WebSphere MQ Service tries to send the messages to all the nodes and the nodes will try processing these messages.

Resolution



Provided following suggestions -
1. enable JMS MDB Listener on all the PRPC nodes
2. deploy PRPC EAR file with the different settings in the ejb-jar.xml file. 

User has enabled JMS MDB Listener on all the PRPC nodes and messages were getting processed without any issues. 
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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