What are the shutdown messages for JBoss EAP 5.x / 4.x

Environment

• JBoss Enterprise Application Platform (EAP)
  • 5
  • 4.3
  • 4.2

Issue

• What are the shutdown messages for JBoss EAP?
• As there are several ways to shutdown a JBoss EAP instance, it logs different messages for each method.

Resolution

These are the shutdown messages for the following actions. Note that some messages (such as Runtime shutdown hook called) are common to multiple causes, so find the best match of all logged messages.

EAP 5.x

• Signal from the operating system (Ctrl+c, kill -HUP <JAVA_PID>, kill -INT <JAVA_PID>, kill -TERM <JAVA_PID>, and so on) or (in EAP 5 or earlier) System.exit call:

    ```
    INFO  [org.jboss.bootstrap.microcontainer.ServerImpl] (JBoss Shutdown Hook) Runtime shutdown hook called, forceHalt: true
    ```
  

• Explicit shutdown request (shutdown.sh or shutdown.bat, shutdown() operation of jboss.system:type=Server MBean from jmx-console, twiddle or JMX Client, shutdown command from CLI or administration console):

    ```
    INFO  [org.jboss.bootstrap.microcontainer.ServerImpl] (http-127.0.0.1-8080-2) Shutting down the server, blockingShutdown: false
    DEBUG [org.jboss.bootstrap.microcontainer.ServerImpl] (http-127.0.0.1-8080-2) exitOnShutdown: true
    DEBUG [org.jboss.bootstrap.microcontainer.ServerImpl] (http-127.0.0.1-8080-2) blockingShutdown: false
    INFO  [org.jboss.bootstrap.microcontainer.ServerImpl] (Thread-21) Server exit(0) called
    INFO  [org.jboss.bootstrap.microcontainer.ServerImpl] (JBoss Shutdown Hook) Runtime shutdown hook called, forceHalt: true
    ```
  
  
    Note: The thread name will be different between invoking the operation from jmx-console and others. It will be `(http-<ip-address>-<port>-XXX` on jmx-console and `(RMI TCP Connection(XXX)-<ip-address>)` on others.
  

• Invoke exit() operation of jboss.system:type=Server MBean from jmx-console, twiddle or JMX Client:

  This does not apply to EAP 5+.

• kill -KILL <JAVA_PID>:

    No output in server.log
  

EAP 4.x

• Signal from the operating system (Ctrl+c, kill -HUP <JAVA_PID>, kill -INT <JAVA_PID>, kill -TERM <JAVA_PID>, and so on) or (in EAP 5 or earlier) System.exit call:

    ```
    INFO  [org.jboss.system.server.Server] Runtime shutdown hook called, forceHalt: true
    ```
  

• Explicit shutdown request (shutdown.sh or shutdown.bat, shutdown() operation of jboss.system:type=Server MBean from jmx-console, twiddle or JMX Client, shutdown command from CLI or administration console):

    ```
    INFO  [org.jboss.system.server.Server] Shutting down the server, blockingShutdown: false
    INFO  [org.jboss.system.server.Server] Server exit(0) called
    INFO  [org.jboss.system.server.Server] Runtime shutdown hook called, forceHalt: true
    ```
  

• Invoke exit() operation of jboss.system:type=Server MBean from jmx-console, twiddle or JMX Client:

    ```
    INFO  [org.jboss.system.server.Server] Server exit(1) called
    INFO  [org.jboss.system.server.Server] Runtime shutdown hook called, forceHalt: true
    ```
  

• kill -KILL <JAVA_PID>:

    No output in server.log
  

Notes

On Linux:

• SIGHUP = 1
• SIGINT = 2
• SIGKILL = 9
• SIGTERM = 15

Please also refer to the following links for additional information regarding "shutdown process":

• Content from community.jboss.org is not included.Shutdown Logs
• This content is not included.Stopping the Server
• This content is not included.Connecting to the JMX Server

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.