|
Problem |
MustGather for when your WebSphere® Application Server is
not responding (hangs) for V3.5 and V4.0 releases on the Microsoft®
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, refer to MustGather:
Read first for all WebSphere Application Server products.
No response (hang) or performance degradation specific MustGather
information
This technote describes what information you need to begin
troubleshooting a Java™ virtual machine (JVM™) that is not responding or
hangs.
Notes:
- In WebSphere Application Server V4.0 releases, do NOT
create DrAdmin.bat. It already exists in the
install_root\bin directory.
- If possible, enable verbosegc before recreating the
problem. Refer to Enabling
verbosegc in WebSphere Application Server for more information.
Perform the following steps when the JVM stops responding (hangs):
- 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
- Enter the following from a command prompt on the WebSphere Application
Server machine and any remote Web server machines:
netstat -an > netstat.out
- Run the following command:
DrAdmin -serverPort Port -dumpThreads
- Wait 2 minutes.
- Run the following command:
DrAdmin -serverPort Port -dumpThreads
- Wait 2 minutes.
- Run the following command:
DrAdmin -serverPort Port -dumpThreads
- Generate a user.dmp. Refer to the following technote for more
information:
MustGather:
Getting user.dmp when Hangs/Performance Degradation prevents generating a
javacore.
- Send everything in the following files:
- Everything in install_root\logs directory. If
your application server stderr and stdout are not in the
logs directory, also include these files.
- netstat.out.
- If you are running version 3.5.4 or later, send all
javacore*.txt files from the \winnt\system32 or
install_root\bin directory.
- Follow instructions the instructions in the following technote: Submitting
Diagnostic Information to IBM Technical Support for Problem
Determination.
Creating the DrAdmin.bat file for V3.5 releases
DrAdmin -serverHost
hostname -serverPort Dr Admin
Port -dumpThreads
To create DrAdmin.bat:
- In the install_root\bin\debug directory, copy
adminserver.bat to DrAdmin.bat
- 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
- Save and close the DrAdmin.bat file.
- Follow instructions the instructions in the following technote: Submitting
Diagnostic Information to IBM Technical Support for Problem
Determination.
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. |
|
|