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

Restart of all PRPC nodes fails on initial attempt



PRPC initialization sporadically fails when multiple nodes are restarted.

Error Messages

From App Server STDOUT log:
JBAS013412: Timeout after [300] seconds waiting for service container stability. Operation will roll back.

From PegaRULES log:
2016-11-15 20:55:56,352 [] [ STANDARD] [ ] [ ] ( internal.mgmt.PRNodeImpl) INFO - Starts joining cluster
2016-11-15 21:01:21,366 [] [ STANDARD] [ ] [ ] ( internal.mgmt.PREnvironment) ERROR - java.lang.IllegalStateException: Node failed to start!
2016-11-15 21:01:21,371 [] [ STANDARD] [ ] [ ] ( etier.impl.EngineStartup) ERROR - PegaRULES initialization failed. Server: PRNodeImpl init failed
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(
Caused by: java.lang.IllegalStateException: Node failed to start!
at com.hazelcast.instance.HazelcastInstanceImpl.<init>(


Steps to Reproduce

Not Applicable 

Root Cause

A configuration setting in the operating environment (the amount of time that the Controller Boot Thread waits for app server startup) was set too low, causing the servers to shut themselves back down.


Make the following change to the operating environment: Adjust the "" in JBOSS configuration file (standalone-*.xml or domain.xml - depending on clustering setup) to increase the value.  Initial value set was 300 seconds, recommended increase to 600 seconds.


Published December 31, 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