What are the shutdown messages for JBoss EAP
Environment
- JBoss Enterprise Application Platform (EAP)
- 7
- 6
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 7.0 Update 4+
-
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.as.server] (Thread-2) WFLYSRV0272: Suspending server INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested via an OS signal ``` -
Explicit shutdown request (
shutdown.shorshutdown.bat,shutdown()operation ofjboss.system:type=ServerMBean from jmx-console, twiddle or JMX Client,shutdowncommand from CLI or administration console):- via JBoss Management CLI like `./bin/jboss-cli.sh -c --commands=shutdown` INFO [org.jboss.as.server] (Management Triggered Shutdown) JBAS015985: Shutting down in response to management operation '{"address" => [],"operation" => "shutdown","operation-headers" => {"caller-type" => "user","access-mechanism" => "NATIVE"}}' - via the HTTP management API like `curl -L -D - http://<management-ip-address>:9990/management --header "Content-Type: application/json" -d '{"operation":"shutdown"}' --digest -u <admin-user>:<admin-passowrd>` INFO [org.jboss.as.server] (Management Triggered Shutdown) JBAS015985: Shutting down in response to management operation '{"operation" => "shutdown","address" => undefined,"operation-headers" => {"access-mechanism" => "HTTP"}}' - via `shutdown` operation in the MBean `jboss.as:management-root=server` INFO [org.jboss.as.server] (Management Triggered Shutdown) JBAS015985: Shutting down in response to management operation '{"operation" => "shutdown","address" => [],"restart" => true,"operation-headers" => {"access-mechanism" => "JMX"}}' -
kill -KILL <JAVA_PID>:No output in server.log
EAP 6.4 Update 11+
-
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.as.server] (Thread-2) JBAS015986: Host Controller shutdown has been requested via an OS signal ``` -
Explicit shutdown request (
shutdown.shorshutdown.bat,shutdown()operation ofjboss.system:type=ServerMBean from jmx-console, twiddle or JMX Client,shutdowncommand from CLI or administration console):- via JBoss Management CLI like `./bin/jboss-cli.sh -c --commands=shutdown` INFO [org.jboss.as.server] (Management Triggered Shutdown) JBAS015985: Shutting down in response to management operation '{"address" => [],"operation" => "shutdown","operation-headers" => {"caller-type" => "user","access-mechanism" => "NATIVE"}}' - via the HTTP management API like `curl -L -D - http://<management-ip-address>:9990/management --header "Content-Type: application/json" -d '{"operation":"shutdown"}' --digest -u <admin-user>:<admin-passowrd>` INFO [org.jboss.as.server] (Management Triggered Shutdown) JBAS015985: Shutting down in response to management operation '{"operation" => "shutdown","address" => undefined,"operation-headers" => {"access-mechanism" => "HTTP"}}' - via `shutdown` operation in the MBean `jboss.as:management-root=server` INFO [org.jboss.as.server] (Management Triggered Shutdown) JBAS015985: Shutting down in response to management operation '{"operation" => "shutdown","address" => [],"restart" => true,"operation-headers" => {"access-mechanism" => "JMX"}}' -
kill -KILL <JAVA_PID>:No output in server.log
Notes
On Linux:
SIGHUP= 1SIGINT= 2SIGKILL= 9SIGTERM= 15
For EAP 5.x and EAP 4.x see: What are the shutdown messages for JBoss EAP 5.x / 4.x
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.