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 configured in WAS failed to start in production



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(
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener.init(
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener.onMessage(
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.


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

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