Friday, September 02, 2005

Application Server crash

Problem
MustGather for problems with a WebSphere� Application Server crash on
the Solaris� platform. Gathering this information before calling IBM
support will help familiarize you with the troubleshooting process and
save you time.
Solution
This document lists what is needed to begin troubleshooting an
Application Server crash on Sun� Microsystems Solaris platform.

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

Crash on Solaris specific MustGather information

1. Important: Before executing any of the following instructions,
please make a backup copy of the core file. Perform the following for
each core file (the core file will be in the working directory, which
is /opt/WebSphere/AppServer/bin by default).

2. If running Solaris 8 or above,enter the following from a command-line:
/usr/proc/bin/pstack [core]>pstack.out
/usr/proc/bin/pmap [core]>pmap.out
/usr/proc/bin/pldd [core]>pldd.out


where:
[core] is the name of the core file
pstack.out is changed for each core file
pmap.out is changed for each core file
pldd.out is changed for each core file


3. If not running Solaris 8 or above and dbx is installed on the
Solaris machine, enter the following from a command-line:

./dbxtrace_sun.sh [executable] [core]>dbxtrace.out


where:
[executable] is opt/WebSphere/AppServer/java/bin/sparc/native_threads/java
[core] is the name of the core file
dbxtrace.out is changed for each core file


4. If not running Solaris 8 or above and gdb is installed on the
Solaris machine, enter the following from a command-line:

./gdbtrace.sh [executable] [core]>gdbtrace.out


where:
[executable] is opt/WebSphere/AppServer/java/bin/sparc/native_threads/java
[core] is the name of the core file
gdbtrace.out is changed for each core file


5. In addition to the preceding information, capture the following:
* For V6.0 release:
o All files in
<install_root>/profiles/<ProfileName>/logs/<ServerName> directory.
o A copy of server.xml located in
<install_root>/profiles/<ProfileName>/config/cells/<CellName>/nodes/<NodeName>/servers/<ServerName>director
* For V5.0 and V5.1 releases:
o Include all of the files from the
<install_root>/logs/<ServerName>directory.
o A copy of server.xml located at
<install_root>/config/cells/<CellName>/nodes/<nodeName>/servers/<ServerName>
directory
* For V3.5 and V4.0 releases:
o Include all of the files from the
<install_root>/logs directory.
o A copy of XMLExport for the server configuration
* env > env.out
* ulimit -a > ulimit.out
* uname -a > uname.out
* showrev -p > showrev.out
* pkginfo -l > pkginfo.out
* /var/adm/messages
* All hs_err_pid*.log files
* Note: For all versions, If you have configured the
Application Server to write logs into a different location, send them
accordingly.
6. Follow instructions tosend diagnostic information to IBM support.

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

Related information
Ten Steps to Getting Support

0 Comments:

Post a Comment

<< Home