WebSphere Application Server & Liberty

Container fails to start with CWOBJ2524E

----

00000001 ServerImpl E CWOBJ2524E: The server failed to complete initialization after 3 minutes.

00000001 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on ****.txt com.ibm.ws.objectgrid.InitializationService.main 738

00000001 Initializatio W CWOBJ0902W: An error prevented the ObjectGrid runtime component from starting for server: con01.

00000001 Initializatio W CWOBJ0006W: An exception occurred: java.lang.reflect.InvocationTargetException

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:83)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57)

at java.lang.reflect.Constructor.newInstance(Constructor.java:437)

at com.ibm.websphere.objectgrid.server.ServerFactory.initialize(ServerFactory.java:407)

at com.ibm.websphere.objectgrid.server.ServerFactory$2.run(ServerFactory.java:310)

at java.security.AccessController.doPrivileged(AccessController.java:678)

at com.ibm.websphere.objectgrid.server.ServerFactory.getInstance(ServerFactory.java:308)

at com.ibm.ws.objectgrid.InitializationService.main(InitializationService.java:306)

Caused by: com.ibm.websphere.objectgrid.ObjectGridRuntimeException: this server is not ready for the container after having waited for 3 minutes

at com.ibm.ws.objectgrid.server.impl.ServerImpl.(ServerImpl.java:1698)

... 9 more

----

Analysis:

If DCSV8050I indicates AV=1 and it's not increased with DCSV1032I, it means this container server has not received a DCS message from other JVMs.

In my case, the other JVMs were having the error below. It seemed the other JVMs didn't send the DCS message to the problematic JVM which was waiting for the event that the number of active JVM becomes greater equal than 2.

Then, this resulted into the startup failure.

-----

CoreStackMemb E HMGR0002E: HA Manager services on this process were not started. This server is not a member of a core group.

-----

Solution:

Cold restart

Possible workaround:

You might be able to start the problematic server with the simultaneous restart of the other server so that the two containers would be able to communicate with each other. But the underlying component like DCS/HA could be under an erroneous condition. So I would recommend the cold restart.