Troubleshooting
Problem
Collecting data for problems with the IBM® WebSphere® Application Server shutting down correctly (not a crash or hang) but there is no apparent reason why this occurs. Gathering this information before calling IBM support helps familiarize you with the troubleshooting process and saves you time.
Resolving The Problem
If you have already contacted support, continue on to the component-specific MustGather information.
Otherwise, click: MustGather: Read first for WebSphere Application Server.
Application Server stopping specific MustGather information
There are a number of reasons why an Application Server can stop for no apparent reason, it is already assumed that the nodeagent did not submit a server shutdown (from nodeagent's SystemOut.log file).
- Client calling System.exit with application code.
- User logging out of the terminal which started the process.
- Closing Windows Terminal Services Client.
- User logging off the machine without services set to keep it running (Windows® only).
- Administration script running in the background to shut the application server down.
If the preceding causes are not the problem, the following will be needed by support to review the problem:
- If you are able to recreate the problem, enable the following trace specification on the application server:
For all releases of WebSphere Application Server
com.ibm.ws.runtime.*=all - If you are unable to recreate the problem, proceed to step 3
- Run the Collector Tool on both the Network Deployment (if applicable) and base nodes.
Follow instructions to send diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials specific to the application server stopping, search the WebSphere Application Server support site.
Related technote:
How to get a thread dump of Javacore during server shutdown
http://www-1.ibm.com/support/docview.wss?uid=swg21304559
Related Information
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21199612