If you already contacted support, continue to the component specific
MustGather information. Otherwise, click: MustGather:
Read first for all WebSphere Application Server products.
To begin solving a problem with DRS in Application Server V5 (all
releases), you must first have a clear understanding of the topology for
the environment, and reproduce the problem with DRS tracing enabled.
DRS specific MustGather information
If possible please provide a simple testcase that has no external
dependancies. If a testcase cannot be provided please collect the
following data.
- Provide a detailed explanation of the topology (number of nodes,
software on each, and so on).
- Cluster configuration.
- Details of each Application Server in the cluster, including the node
on which the Application Server exists (hardware platform, operating
system of this node, and so on).
- Replication domain configuration details along with individual
replicators.
- Go to the install_root/config directory on
the deployment manager and capture the entire contents into a .zip file,
Config.zip.
- Collect the following trace depending on how you are using DRS.
- If Dynamic Cache is the DRS client in the WebSphere deployment,
enable dynamic cache tracing. Dynamic cache trace specification:
com.ibm.ws.cache.*=all=enabled:
com.ibm.ws.drs.*=all=enabled |
|
- If session is the DRS client, enable session tracing. Session
trace specification:
com.ibm.ws.webcontainer.httpsession.*=all=enabled:
com.ibm.ws.drs.*=all=enabled:
com.ibm.ws.cache.*=all=enabled |
For detailed instructions on enabling trace please see How
to setup a Trace |
- Backup and remove all of the log files in the
install_root/logs directory for the Application
Server.
- Reproduce the problem.
- When do you see the problem?
- What steps did you take to reproduce the problem?
- Generate the historyReport.html by running the tool
genHistoryReport.bat or genHistoryReport.sh, which is
located in install_root\bin directory.
Historyreport.html is generated in the working directory from
which the genHistoryReport tool is run.
- Collect the following files:
- Config.zip (from step 2)
- Trace.log
- SystemOut.log
- SystemErr.log
- native_stderr
- native_stdout
- FFDC logs with the current date from the
install_root/logs/ffdc directory.
- Historyreport.html (from step 17)
- Follow instructions to send
diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials
specific to the DRS component, search the WebSphere
Application Server support site. |