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

Delayed restart of JVM's in production

SA-32010

Summary



Production agent nodes takes long time to start.


Error Messages



2016-12-17 08:24:59,340 INFO  [STDOUT] (Dispatcher-Thread-107) 2016-12-17 08:24:59,306 [   WorkManager(2)-22] [          ] [                    ] (       etier.mdb.PRJMSListener) ERROR   - PRPC Engine invocation failed, javax.ejb.EJBException: Unable to locate implementation of PegaRULES Engine class for EngineBMT
2016-12-17 08:24:59,341 SEVERE [com.pega.pegarules.internal.bootstrap.PRBootstrap] (WorkManager(2)-22) Problem during method invocation (onMessage)
javax.ejb.EJBException: Unable to locate implementation of PegaRULES Engine class for EngineBMT


Steps to Reproduce



Not Applicable


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




Ensure that all the messages in the queue are drained before restarting the server.

 

Published January 24, 2017 - 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