Support Article
After Pega722 upgrade on JBoss 6.4 server is not coming up
SA-40767
Summary
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 [org.jboss.as.controller.management-operation] (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 [org.jboss.as.server] (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 [org.jboss.as.controller.management-operation] (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 org.jboss.as.controller.OperationContextImpl.waitForRemovals(OperationContextImpl.java:275) [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1171) [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1124) [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1084) [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1044) [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext.handleContainerStabilityFailure(AbstractOperationContext.java:857) [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:534) [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:338) [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:314) [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1152) [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:335) [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:204) [jboss-as-controller.jar:7.5.14.Final-redhat-2]
at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:306) [jboss-as-domain-http-interface.jar:7.5.14.Final-redhat-2]
at org.jboss.as.domain.http.server.DomainApiHandler.doHandle(DomainApiHandler.java:181) [jboss-as-domain-http-interface.jar:7.5.14.Final-redhat-2]
at org.jboss.as.domain.http.server.DomainApiHandler.safeHandle(DomainApiHandler.java:197) [jboss-as-domain-http-interface.jar:7.5.14.Final-redhat-2]
at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:189) [jboss-as-domain-http-interface.jar:7.5.14.Final-redhat-2]
at org.jboss.as.domain.http.server.security.SubjectAssociationHandler$1.run(SubjectAssociationHandler.java:69) [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 jboss.as.controller: BlockingTimeout.
This class loads the value of system property jboss.as.management.blocking.timeout or defaults to 300 (seconds).
Resolution
Add below property in standalone-full.xml and server starts up successfully:
<system-properties>
<property name="jboss.as.management.blocking.timeout" value="600"/>
</system-properties>Published October 4, 2017 - 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.