Support Article

Multiple JMS MDB listener instances available in SMA

SA-30535

Summary



Multiple JMS MDB listener instances available in System Management Application (SMA). Listener stops picking the messages from queue. MDB Listener starts working again after server restart but again stops after some time.

Error Messages



com.pega.pegarules.internal.bootstrap.PRBootstrap  Problem during method invocation (onMessage)
                java.lang.IllegalStateException: getRollbackOnly can not be called without a Transaction Context
DeliveryHelpe E com.solacesystems.jms.ra.inbound.async.DeliveryHelper deliver Unable to deliver non-transacted message to MDB : nested exception is: java.lang.RuntimeException: Problem during method invocation (onMessage) jmsResource instance?
 [com.solacesystems.jms.ra.inbound.async.InboundJmsResource@6fb76fb7] beforeDeliveryCalled?[null] refreshException [null]: null endPoint [ PRPCE114#prbeans.jar#SendCorrInputResponseListener($Proxy@323e323e)] helper [ com.solacesystems.jms.ra.inbound.async.DeliveryHelper@1ebe1ebe]
                                 com...ejs.container.UnknownLocalException: nested exception is: java.lang.RuntimeException: Problem during method invocation (onMessage)

Steps to Reproduce

1. Open the SMA.
2. Check the list of Running listeners.


Root Cause



Even though there are multiple MDB Listeners available in SMA they are not processing the pending messages in queue, because the JMS destination was not configured properly to send messages in transaction context.

Resolution



Due to third party JMS destination the messages were not delivered to the MDB Listener, user is suggested to configure the destination JMS queue properly.
 

 

Published November 18, 2016 - Updated November 28, 2016

Have a question? Get answers now.

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