|
Problem(Abstract) |
Collecting data for problems with the IBM® WebSphere®
Application Servershutting 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 all WebSphere Application Server products.
Application Server stopping specific MustGather information
There are a number of reasons why an Application Server can stop for no
apparent reason, we already assume that the nodeagent did not submit a
server shutdown (the file SystemOut.log from the nodeagent log)
- 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, run the following trace on
the application server:
Admin=all=enabled:com.ibm.ws.runtime.*=all=enabled |
|
If you are unable to recreate the problem, proceed to
step 2. |
|
- 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. |
|
|
|