search cancel

IM fails to start on JBoss EAP 6.x with JBAS013412 error on startup after Step 5 of IM startup.


Article ID: 37761


Updated On:


CA Identity Manager CA Identity Governance CA Identity Portal CA Risk Analytics CA Secure Cloud SaaS - Arcot A-OK (WebFort) CLOUDMINDER ADVANCED AUTHENTICATION CA Secure Cloud SaaS - Advanced Authentication CA Secure Cloud SaaS - Identity Management CA Secure Cloud SaaS - Single Sign On



IM fails to start on JBoss EAP 6.x with JBAS013412 error on startup after Step 5 of IM startup.

The log will have something similar to this:

16:13:45,504 ERROR [] (Controller Boot Thread) JBAS013412: Timeout after [300] seconds waiting for service container stability. Operation will roll back. 


Any version of IM r12.6 running on JBoss EAP 6.x


The building of Identity Manager's roles cache takes longer than the JBoss timeout will allow. Step 5 of the IM startup sequence is the lengthiest of all of them, since this is where IM loads all of the admin, provisioning and access roles and calculates the valid users for each of them and writes them to an in memory cache to allow users quick logins.

Starting in JBoss EAP 6.0, the timeout for any thread is lower than what IM typically can process the caches with.


Modify the .bat or .sh file that you use to start JBoss. For most installations, this is the standalone.bat or file.

Find the line with:


Here you will see a series of "-D" flags.

Add this additional flag:<xxx>

You'll need to determine the value of "xxx"

By default this is set to 300 seconds. If you know you have many IM roles and users, you may want to set this to something very high like 3600 for one hour. You will have to look at your previous server startup times and make sure what setting to use.

Additional Information:


Release: CAIDMB99000-12.6.7-Identity Manager-B to B