MustGather: WebSphere Application Server start and stop problems
 Technote (troubleshooting)
 
Problem(Abstract)
Collecting data for problems starting and stopping IBM® WebSphere® Application Server versions 5.0 and 5.1. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.
 
Resolving the problem

Do you want to automate the collection of MustGather data?
You can automatically collect this data using IBM Support Assistant (ISA) Lite
- a special offering that contains the data collector component of the IBM Support Assistant Workbench.

For a full range of problem-solving features, install the IBM Support Assistant Workbench - your support workbench for finding answers and solving problems. The workbench contains all the data collection capability of ISA Lite plus much more!

If you have already contacted support, continue on to the component specific MustGather information. Otherwise, click on the following link: MustGather: Read first for all WebSphere Application Server products.

Application server start and stop specific MustGather information
If an Application Server is not able to start when issuing the command startserver server_name at the command line, or if an Application Server is unable to start or stop using the Network Deployment Web console, collect the following documents using one of the following tracing methods:
  • Starting or stopping the server from a command line
    • Backup and purge the logs in the following directories:

      install_root/logs/server_name
      install_root/logs/FFDC

    • Edit the server.xml file located in the following directory:

      install_root/config/cells/cell_name/nodes/node_name/servers/server_name

    • Find the TraceService XML tag section.

    • Modify the startup Trace Specification entry to look like the following:

      *=all=enabled

    • Make sure enable is set to true.

    • Save the file.

    • Run the following command:

      startServer server_name -trace

      Note: For stopServer problems, run the following command:

      stopServer server_name -trace

      You might have to kill the Java process and then recreate the problem. The trace set in the server.xml file will not be effective until we recycle the server.

    • Run the collector tool on the base node. See the Information Center specific to the version of Application Server you are running for additional information.

    • Follow instructions to send diagnostic information to IBM support.

  • Starting or stopping the server from the Deployment Manager Administrative Console
    1. Set up the trace on failing server
      • Backup and purge the logs in the following directories:

        install_root/logs/server_name
        install_root/logs/nodeagent_name
        install_root/logs/FFDC

      • In the administrative console, expand Troubleshooting and click Logs and Trace.

      • Click on the link for your server.

      • Click on Diagnostic Trace.

      • In the Trace Specification field, enter the following:

        *=all=enabled

      • Click Apply.

      • Save and sync your configuration.

    2. Set up the trace of nodeagent
      • In the administrative console, expand Troubleshooting and click Logs and Trace.

      • Click on the nodeagent.

      • Click on Diagnostic Trace.

      • In the Trace Specification field, enter the following:

        Admin=all=enabled

      • Click Apply.

      • Save and sync your configuration.

    3. Restart the nodeagent.

    4. Recreate the problem. Start the Application Server.

      Note: For stop server problems from the administrative console, stop the server from a command prompt or kill the Java™ process. Then, recreate the problem from the administrative console. Trace enabled on the administrative console will not be effective until you recycle the server.

    5. Run the collector tool on the base node. See the Information Center specific to the version of WebSphere Application Server you are running for additional information.

    6. Follow instructions to send diagnostic information to IBM support.

For a listing of all technotes, downloads, and educational materials specific to the Administration Server, search the WebSphere Application Server support site.

 
Related information
Submitting information to IBM support
Steps to getting support
MustGather: Readme first
Troubleshooting guide
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > System Management/Repository
Operating system(s): Windows
Software version: 5.1
Software edition:
Reference #: 1141075
IBM Group: Software Group
Modified date: Feb 16, 2007