MustGather: No response (hang) or performance degradation on Windows® for V3.5 and V4.0 releases

Technote (FAQ)
Problem
MustGather for when your WebSphere® Application Server is not responding (hangs) for V3.5 and V4.0 releases on the Windows platform. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.
Solution
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.

No response (hang) or performance degradation specific MustGather:

This technote describes what information you need to begin troubleshooting a Java™ virtual machine (JVM™) that is not responding or hangs.

Notes:
  1. In WebSphere Application Server V4.0 releases, do NOT create DrAdmin.bat. It already exists in the $WAS_HOME\bin directory.

  2. If possible, enable verbosegc before recreating the problem.


Perform the following steps when the JVM stops responding (hangs):
  1. Capture a DrAdmin dump on your application server at the time of the hang. If you are running on any release of version 3.5, see the section Creating the DrAdmin.bat file for V3.5 releases below.

    To determine the ServerPort to use, look in the stdout for the application server that is hung for the most recent entry similar to:

    DrAdminServer A SMTL0018I: DrAdmin available on port 3,401
  2. Enter the following from a command prompt on the WebSphere Application Server machine and any remote Web server machines:

    netstat -an > netstat.out

  3. Run the following command:

    DrAdmin -serverPort Port-dumpThreads

  4. Wait 2 minutes.

  5. Run the following command:

    DrAdmin -serverPort Port-dumpThreads

  6. Wait 2 minutes.

  7. Run the following command:

    DrAdmin -serverPort Port-dumpThreads

  8. Generate a user.dmp. See technote,
    MustGather: Getting user.dmp when Hangs/Performance Degradation prevents generating a javacore.

  9. Send everything in the following files:
    1. Everything in $WAS_HOME\logs directory. If your application server stderr and stdout are not in the logs directory, also include these files.

    2. netstat.out.

    3. If you are running version 3.5.4 or later, send all javacore*.txt files from the \winnt\system32 or $WAS_HOME\bin directory.

Creating the DrAdmin.bat file for V3.5 releases

DrAdmin -serverHost hostname-serverPort Dr Admin Port -dumpThreads

To create DrAdmin.bat:
  1. In the $WAS_HOME\bin\debug directory, copy adminserver.bat to DrAdmin.bat

  2. Replace the following line in the DrAdmin.bat file (replace the entire line):

    %JAVA_HOME%\bin\java -mx128m com.ibm.ejs.sm.server.AdminServer -bootFile %WAS_HOME%\bin\admin.config %restart% %1 %2 %3 %4

    with

    %JAVA_HOME%\bin\java com.ibm.ejs.sm.util.debug.DrAdmin %1 %2 %3 %4 %5%6 %7 %8 %9

  3. Save and close the DrAdmin.bat file.
  4. Follow instructions tosend diagnostic information to IBM support.

For a listing of all technotes, downloads, and educational materials specific to the Hangs or Performance Degradation component, search the WebSphere Application Server support site.

Related information
How to enable verbosegc for WebSphere

Ten Steps to Getting Support












Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Hangs/Performance Degradation
Operating system(s): Windows 2000, Windows NT
Software version: 3.5, 4.0
Software edition: Edition Independent
Reference #: 1052640
IBM Group: Software Group
Modified date: 2004-12-08