BEA-000388 - JVM called WLS shutdown hook. The server will force shutdown now
BEA-000388 - JVM called WLS shutdown hook. The server will force shutdown now
Issue
- WebLogic Server shuts down with the similar errors in log files
<Apr 24, 2009 12:10:44 PM PDT> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
<Apr 24, 2009 12:10:44 PM PDT> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
<Apr 24, 2009 12:10:44 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Possible Cause and Solution
- I have the following suggestion for you for the below error:
<Apr 24, 2009 12:10:44 PM PDT> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
It seems like some component is sending the kill interrupt to JVM
VM monitors and catches OS signals, like: CTRL +C event, Log off event, shutdown event.When JVM catches one of the stated above signals, it shutdowns all java processes.**
Try adding this jvm parameter to your WebLogicServer’s JVM options
-Xrs
- Specify -Xrs parameter in the JAVA startup arguments and start the WebLogic Server
- Note: -Xrs is a non-standard option developed by Sun Microsystems for their HotSpot JVM. BEA JRockit continues to support this option; however the BEA JRockit non-standard option -XnoHup provides the same functionality. -Xrs reduces usage of operating-system signals by the JVM. If the JVM is run as a service (for example, the servlet engine for a web server), it can receive CTRL_LOGOFF_EVENT but should not initiate shutdown since the operating system will not actually terminate the process. To avoid possible interference such as this, the -Xrs command-line option does not install a console control handler, implying that it does not watch for or process CTRL_C_EVENT, CTRL_CLOSE_EVENT, CTRL_LOGOFF_EVENT, or CTRL_SHUTDOWN_EVENT Operation.
If the issue still persists try adding the following parameter to your JAVA_OPTION
- Depending on the JVM version, it may be possible to get a thread dump before the process exits
- HotSpot supports the command-line option -XX:+ShowMessageBoxOnError
- The corresponding JRockit option is -Djrockit.waitonerror
- While the JVM< goes down, it may prompt the user: “Do you want to debug the problem?”
- This pauses the JVM, thereby creating an opportunity to generate a thread dump (a stack trace of every thread in the JVM), attach a debugger, or perform some other debugging activity.
Cheers :)
Unni