|
Problem(Abstract) |
Collecting data for when your IBM® WebSphere® Application
Server is not responding (hangs) on a Solaris operating system. Gathering
this information before calling IBM Support will help familiarize you with
the troubleshooting process and save you time. |
|
|
|
Resolving the
problem |
If you have already contacted support, continue 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
information
Follow these instructions for initial environment set up before you
re-create the hang problem:
- If possible, following instructions on Enabling
verbosegc on WebSphere Application Server before recreating the
problem.
- Synchronize clocks on all Web server and WebSphere Application Server
systems. If clocks on the Web server and WebSphere Application Server
systems were not synchronized for some reason, provide information which
clock was faster and what was the difference.
- If possible, clean all Web server, plug-in and WebSphere Application
Server and FFDC logs.
To begin troubleshooting your problem, execute the following commands
during the time when the WebSphere Application Server system JVM does not
respond:
- Run the following command
netstat -an > netstat.out |
|
- Run the following command:
lsof -p
[PID_of_hung_JVM] > lsof.out |
|
- Run the following command:
vmstat 5 12 > vmstat1.out |
|
- Run the following command:
/usr/proc/bin/pfiles
[PID_of_hung_JVM] > pfiles.out |
|
- Run the following command:
/usr/proc/bin/pmap
[PID_of_hung_JVM] > pmap.out |
|
- Run the following command:
/usr/proc/bin/pstack
[PID_of_hung_JVM] > pstack1.out |
|
- Run the following command:
kill -3
[PID_of_hung_JVM] |
|
- Wait two minutes.
- Run the following command:
/usr/proc/bin/pstack
[PID_of_hung_JVM] > pstack2.out |
|
- Run the following command:
kill -3
[PID_of_hung_JVM] |
|
- Wait two minutes.
- Run the following command:
/usr/proc/bin/pstack
[PID_of_hung_JVM] > pstack3.out |
|
- Run the following command:
kill -3
[PID_of_hung_JVM] |
|
- Run the following command:
vmstat 5 12 > vmstat2.out |
|
- Capture the following machine environment information:
env > env.out
ulimit -a > ulimit.out
uname -a > uname.out
showrev -p > showrev.out
pkginfo -l > pkginfo.out |
|
- Gather the following files:
- For WebSphere Application Server V6.0:
- The server.xml file located in the following
directory:
profile_root/config/cells/cell_name/nodes/
node_name/servers/server_name |
|
- plugin-cfg.xml and http_plugin.log
- Everything in the following directory:
profile_root/logs/server_name |
|
- Everything in the following directory:
- All documents requested for all releases below
- For WebSphere Application Server V5.0 and 5.1:
- The server.xml file located in the following
directory:
install_root/config/cells/nodes/node_name/
servers/server_name |
|
- plugin-cfg.xml and http_plugin.log
- Everything in the following directory:
install_root/logs/server_name |
|
- Everything in the following directory:
- All documents requested for all releases below
- For all releases:
- All of the preceding *.out files collected
- Include the Application Server native_stderr and
native_stdout, if they are located in a different directory
- The Web server access and error logs
- Follow instructions to send
diagnostic information to IBM support.
If you want to analyze the Java™ thread dumps yourself, download the ThreadAnalyzer
tool. ThreadAnalyzer is a technology preview that can analyze thread
dumps from WebSphere Application Server. It is useful for identifying
deadlocks, contention, and bottlenecks, as well as summarizing the state
of threads within the Application Server.
For all technotes, downloads, and educational materials specific to a
hang or performance degradation, search the WebSphere
Application Server Support site. |
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
WebSphere Application Server - Express |
Hangs/performance degradation |
Solaris |
6.0, 5.1, 5.0 |
|
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|