MustGather: Data replication service (DRS) problems in versions V5.0 and V5.1
 Technote (troubleshooting)
 
Problem(Abstract)
Collecting data for problems with the IBM® WebSphere® Application Server data replication service (DRS) component.

Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.
 
Resolving the problem

1. Learning more 2. Troubleshooting 3. Collecting data

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.
  1. Provide a detailed explanation of the topology (number of nodes, software on each, and so on).
    1. Cluster configuration.
    2. 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).
    3. Replication domain configuration details along with individual replicators.
  2. Go to the install_root/config directory on the deployment manager and capture the entire contents into a .zip file, Config.zip.
  3. Collect the following trace depending on how you are using DRS.
    1. 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

    2. 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
  4. Backup and remove all of the log files in the install_root/logs directory for the Application Server.
  5. Reproduce the problem.
  6. When do you see the problem?
  7. What steps did you take to reproduce the problem?
  8. 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.
  9. Collect the following files:
    1. Config.zip (from step 2)
    2. Trace.log
    3. SystemOut.log
    4. SystemErr.log
    5. native_stderr
    6. native_stdout
    7. FFDC logs with the current date from the install_root/logs/ffdc directory.
    8. Historyreport.html (from step 17)
  10. 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.
 
Related information
Submitting information to IBM support
Steps to getting support
MustGather: Read first
Troubleshooting guide
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Data Replication Services
Operating system(s): Windows
Software version: 5.1.1
Software edition:
Reference #: 1164068
IBM Group: Software Group
Modified date: May 25, 2007