Jboss 6.3 timeout setting deploying Identitymanager
Article ID: 41662
Updated On:
Products
Issue/Introduction
Issue:
You are at start up step 5, and that is the longest startup step in the IM steps.
This step is where it is loading environments and contacting the provisioning servers to read Provisioning roles, account templates, and endpoint properties.
The more of these objects there are the longer this step takes.
*** You receive this error: JBAS014781
ERROR [org.jboss.as.controller.client] (Controller Boot Thread) JBAS014781: Step handler org.jboss.as.domain.manage[email protected]3c34b64e for operation {"address" => [("core-service" => "management"),("security-realm" => "ApplicationRealm")],"operation" => "add","map-groups-to-roles" => undefined} at address [
("core-service" => "management"),
("security-realm" => "ApplicationRealm")
Cause:
https://developer.jboss.org/thread/250515
Re: Jboss EAP 6.3 :[org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS013412:
Jay Kumar SenSharma Master
Due to the message [JBAS013412: Timeout after [300] seconds waiting for service container stability.] it looks like a timeout issue , may be your application deployment/ other management operations taking longer than 300 seconds (300 sec is the default value). So try testing with a larger value to see if you still face the same issue or not?
Resolution:
You can try increasing this value to a higher value using the following system property:
-Djboss.as.management.blocking.timeout=700
it is unique to your customer environment and will need to be tuned.
Some customers take 5 minutes at this step: 300 seconds
Some customers take 10 minutes at this step: 600 Seconds
Some customers even take 2 hours at this step: 7200 seconds.
You will have to look at your previous server startup times and make sure what setting to use.
Environment
Component:
Feedback
