Support Article
JMS MDB listener configured in WAS failed to start in production
SA-28503
Summary
User configured JMS MDB listener in production and it failed to start when tried from WAS admin console.
Error Messages
9/22/16 16:08:39:750 EDT] 00000079 SystemOut O 2016-09-22 16:08:39,750 [stenerThreadPool : 1] [ STANDARD] [ ] ( etier.mdb.PRJMSListener) ERROR - PRPC Engine invocation failed, javax.ejb.EJBException: Unable to locate implementation of PegaRULES Engine class for EngineBMT
[9/22/16 16:08:39:750 EDT] 000000e5 PRBootstrap E com.pega.pegarules.internal.bootstrap.PRBootstrap Problem during method invocation (onMessage)
javax.ejb.EJBException: Unable to locate implementation of PegaRULES Engine class for EngineBMT
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener.callEngine(PRJMSListener.java:200)
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener.init(PRJMSListener.java:175)
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener.onMessage(PRJMSListener.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
......
Steps to Reproduce
Add new MDB listener to configuration and push to production.
Root Cause
A defect or configuration issue in the operating environment, likely due to the fact that there were messages in the queue during server startup.
Depending on the timing of the message processing, the Pega engine may not be ready, and hence the error described above.
Resolution
Make the following change to the operating environment:
Ensure that all the messages in the queue are drained before restarting the server.
Published October 15, 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.