MustGather: Dynamic cache problems in V5.0
 Technote (troubleshooting)
 
Problem(Abstract)
Collecting data for problems with the IBM® WebSphere® Application Server Dynamic cache component.

Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.
 
Resolving the problem
If you already contacted support, continue to the component-specific MustGather information. Otherwise, click: MustGather: Read first for all WebSphere Application Server products.

Dynamic cache specific MustGather information
The first step in solving a problem with Dynamic cache in Application Server V5.0 (all releases) is to reproduce the problem with Dynamic cache tracing enabled. This will give you a clear understanding of the environment's topology.

  1. Run genHistoryReport.bat or genHistoryReport.sh which is located in install_root/profiles/profile_name/bin directory, historyreport.html will be generated your working directory.
  2. Clear all Application Server logs:
    • native_stderr, native_stdout, SystemErr and SystemOut logs for your Application Server.
    • They are located in install_root/profiles/profile_name/logs/server_name directory.
    • If you have configured to write Application Server log files into a different location, then clear them accordingly.
    • Clear all WebSphere Application Server FFDC logs. FFDC files are located in install_root/profiles/profile_name/logs/ffdc directory. If you have configured to write FFDC log files into a different location, then clear them accordingly.

  3. Stop Web server.
  4. Delete all Web server logs and http_plugin.log on the Web server system.
  5. Enable full plug-in trace. To perform a plug-in trace.
  6. Start the Web Server
  7. Important: Synchronize clocks on all Web server and Application Server systems.
  8. Collect the following trace
    • Dynacache replication is disabled
      com.ibm.ws.cache.*=all=enabled
    • Dynacache replication is enabled
      com.ibm.ws.cache.*=all=enabled:com.ibm.ws.drs.*=all=enabled

      For detailed instructions on enabling trace please see How to setup a Trace
When you recreate problem:

Capture the following data.
  1. Were clocks synchronized?.
  2. The Application Server logs such as native_stderr, native_stdout, SystemErr, SystemOut, and trace logs
  3. FFDC logs with the current date from install_root/logs/ffdc directory
  4. Complete WebSphere configuration - the entire content from the
    install_root/config directory under the Deploymant Manager profile. Compress the content into a .zip file (for example: Config.zip).
  5. The http_plugin.log file
  6. The plugin-cfg.xml file
  7. The Web server configuration files, such as httpd.conf for HTTP Server.
  8. The Web server logs, such as access and error logs for HTTP Server.
  9. The historyReport.html file from running genHistoryReport.bat or genHistoryReport.sh.
  10. Cluster configuration, details of each application server in the cluster, including the node on which the Application Server exists, replication domain configuration details along with individual replicators.
Follow instructions to send diagnostic information to IBM support.

For a listing of all technotes, downloads, and educational materials specific to the Dynamic cache 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 > Dynamic Cache
Operating system(s): Windows
Software version: 5.1
Software edition:
Reference #: 1163653
IBM Group: Software Group
Modified date: Feb 28, 2007