Support Article

JMS MDB Listener in production env is going down intermittantly

SA-29078

Summary



 JMS listener configured to listen to MQ Topic. After a release in Production, the Listener is getting down intermittently, however the code which was deployed was not related to Listener code.

The change was related to bug fix which was related to Soap Service call.


Error Messages



ERROR   - Failed to create MDB Listener, could not find Listener definition for Data-Admin-Connect-JMSMDBListener:(com.pega.pegarules.integration.engine.internal.services.jms.JMSListener)
com.pega.pegarules.pub.PRException: Listener is not enabled for node: gbl02767
From: (A27D8BDFC54CE15F08321A212E834285B)
    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)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:744)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.createMDBListener(ListenerStateManagerImpl.java:1062)
    at com.pega.pegarules.integration.engine.internal.services.jms.JMSListenerServant.invoke(JMSListenerServant.java:100)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:312)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:263)
    at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.invokeEngine(EngineBean.java:236)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)


Steps to Reproduce



1) Start the Listener .
2) Check if MQ Subscription is up.
3) Listener is going down , after it is restarted.


Root Cause



The application is not pointing to current temp directory, that is, it is pointing to old temp directory with old cache data, which is causing issue while calling MDB Listener.

Resolution



User is suggested to clear cache in old temp directory and restart the server. Issue gets resolved after pointing to current temp directory.

 

Published October 12, 2016 - Updated November 4, 2016

Have a question? Get answers now.

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