WebSphere Application Server stopped automatically after network cable was unplugged

If you find that your application server stopped automatically after a network cable was unplugged or some sort of adverse network event, please look for the following stack trace in the SystemOut.log

[6/30/11 9:50:19:339 EDT] 00000018 SystemOut     O Panic:component requested panic from isAlive
[6/30/11 9:50:19:339 EDT] 00000018 SystemOut     O java.lang.RuntimeException: emergencyShutdown called:
[6/30/11 9:50:19:339 EDT] 00000018 SystemOut     O     at com.ibm.ws.runtime.component.ServerImpl.emergencyShutdown(ServerImpl.java:633)
[6/30/11 9:50:19:339 EDT] 00000018 SystemOut     O     at com.ibm.ws.hamanager.runtime.RuntimeProviderImpl.panicJVM(RuntimeProviderImpl.java:92)
[6/30/11 9:50:19:339 EDT] 00000018 SystemOut     O     at com.ibm.ws.hamanager.coordinator.impl.JVMControllerImpl.panicJVM(JVMControllerImpl.java:56)
[6/30/11 9:50:19:339 EDT] 00000018 SystemOut     O     at com.ibm.ws.hamanager.impl.HAGroupImpl.doIsAlive(HAGroupImpl.java:866)
[6/30/11 9:50:19:339 EDT] 00000018 SystemOut     O     at com.ibm.ws.hamanager.impl.HAGroupImpl$HAGroupUserCallback.doCallback(HAGroupImpl.java:1364)
[6/30/11 9:50:19:339 EDT] 00000018 SystemOut     O     at com.ibm.ws.hamanager.impl.Worker.run(Worker.java:64)
[6/30/11 9:50:19:339 EDT] 00000018 SystemOut     O     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)

Look for any  HMGR informational messages like HMGR0130I that indicate why the JVM was terminated.
If you using SIBus read this technote http://www-01.ibm.com/support/docview.wss?uid=swg21496900


From technote
"WebSphere Application Server uses database tables to store Java Message Service (JMS) messages. Anytime the messaging engine loses its connection to the data store, the JVM shuts down in an orderly fashion to prevent data loss. If the messaging engine were to continue to run and accept work, results might be unpredictable and your messaging engine might be in an inconsistent state when the data store connection is restored.

If you continually see this problem, consider modifying the Retry Interval for your data source. This value specifies the length of time, in seconds, that the application server waits before retrying to make a connection if the initial attempt fails. By default, this value is 0. If you set the value to 3, the connection is retried instead of holding onto a bad connection. You can find more information on datasource properties in the WebSphere Application Server data source properties topic within the WebSphere Application Server Information Center. "

Happy Debugging :)