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

After Pega722 upgrade on JBoss 6.4 server is not coming up



User is getting the error messages while deploying the prpc_j2ee14_jboss61JBM.ear after Pega 7.2.2 upgrade on JBoss 6.4 server.

Server is not starting up due to below error messages.

Error Messages

JBAS013487: Operation timed out awaiting service container stability",
"rolled-back" => true,

15:17:50,252 ERROR [] (HttpManagementService-threads - 6) JBAS013412: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'deploy' at address '[("deployment" => "prpc_j2ee14_jboss61JBM.ear")]'

15:17:50,267 ERROR [] (HttpManagementService-threads - 6) JBAS015870: Deploy of deployment "prpc_j2ee14_jboss61JBM.ear" was rolled back with the following failure message: "JBAS013487: Operation timed out awaiting service container stability"
15:17:55,268 ERROR [] (HttpManagementService-threads - 6) JBAS014781: Step handler [email protected] for operation {"address" => [("deployment" => "prpc_j2ee14_jboss61JBM.ear")],"operation" => "deploy","operation-headers" => {"access-mechanism" => "HTTP"}} at address [("deployment" => "prpc_j2ee14_jboss61JBM.ear")] failed handling operation rollback -- java.util.concurrent.TimeoutException: java.util.concurrent.TimeoutException
at [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at$Step.handleResult( [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at$Step.finalizeInternal( [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at$Step.finalizeStep( [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at$Step.access$300( [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at [jboss-as-domain-http-interface.jar:7.5.14.Final-redhat-2]
at [jboss-as-domain-http-interface.jar:7.5.14.Final-redhat-2]
at [jboss-as-domain-http-interface.jar:7.5.14.Final-redhat-2]
at [jboss-as-domain-http-interface.jar:7.5.14.Final-redhat-2]
at$ [jboss-as-domain-http-interface.jar:7.5.14.Final-redhat-2]

Steps to Reproduce

Not Applicable

Root Cause

From JBoss EAP 6.3.0.ER8 there is a new class in BlockingTimeout.

This class loads the value of system property or defaults to 300 (seconds).


Add below property in standalone-full.xml and server starts up successfully:

         <property name="" value="600"/> 

Published October 4, 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