DFHSJ0210 SETUP_CLASS_TIMEDOUT during CICS TS 5.2 Java Liberty Profile Initialization

For a JVMServer the setup class timeout is controlled by the OSGI_FRAMEWORK_TIMEOUT JVM server option. The default is 60 seconds but you can change it in your JVM profile. As stated in the CICS documentation:

OSGI_FRAMEWORK_TIMEOUT=60|number
Specifies the number of seconds that CICS waits for the OSGi framework to initialize or shut down before timing out. You can set a value 1 - 60000 seconds. The default value is 60 seconds. If the OSGi framework takes longer to start than the specified number of seconds, the JVM server fails to initialize...

I would suggest you try increasing the value by setting OSGI_FRAMEWORK_TIMEOUT=300 in your jvmprofile. After making this change, see if your JVM server initializes. You might have to increase the value a few times to get it right for your environment.

If after changing the OSGI_FRAMEWORK_TIMEOUT, you notice that you are getting the following new message in your dfhjvmerr file:

com.ibm.cics.router.wlp.internal.LibertyServerImpl.waitForServerStart:Liberty profile: Server has not started after 60000 milliseconds

This indicates that the JVMServer initialization timed out again. But this time, it is due to the Java system property variable: com.ibm.cics.jvmserver.controller.timeout

In this case, make sure you have both the following set in you Java Liberty Profile configuration:

OSGI_FRAMEWORK_TIMEOUT=300
Dcom.ibm.cics.jvmserver.controller.timeout=300000

Another option to try is using a shared class cache, add the -Xshareclasses option to the JVM profile of each JVM server. For more information on this topic see Tuning the JVM server startup environment. Also see Shared class cache.