Troubleshooting the dynamic cache service

This page includes steps to troubleshoot the dynamic cache service.

Complete the steps below to resolve problems that you think are related to the dynamic cache service.

 

1. Review the logs. Messages that are prefaced with DYNA result from dynamic cache service operations.

   For distributed platforms, review the JVM logs for the appserver.

   1. On distributed platforms, view the JVM logs for the appserver. Each server has its own JVM log file. For example, if the server is named Member_1, the JVM log is located in...

      install_root/logs/Member_1

      To use the administration console to review the JVM logs, click Troubleshooting > Logs and trace > myserver > JVM logs > Runtime > View.

   2. Find any messages prefaced with DYNA in the log we are viewing, and write down the message IDs. A sample message having the message ID DYNA0030E follows:

      DYNA0030E: "property" element is missing required attribute "name".
      

   3. Find the message for each message ID in the information center for WAS. In the information center navigation tree, click product_name > Reference > Troubleshooter > Messages > DYNA to view dynamic cache service messages.

   4. Read the message Explanation and User Action statements. A search for the message ID DYNA0030E displays a page having the following message:

      DYNA0030E: "property" element is missing required attribute "name".
        Explanation: A required attribute was missing in the cache configuration.
        User Action: Add the required attribute to the cache configuration file.
      

      This explanation and user action suggests that we can fix the problem by adding or correcting a required attribute in the cache configuration file.

   5. Try the solutions stated under User Action in the DYNA messages.

2. Use the cache monitor to determine whether the dynamic cache service is functioning as expected. The cache monitor is an installable Web app that displays simple cache statistics, cache entries, and cache policy information.

3. If we have completed the preceding steps and still cannot resolve the problem, contact the IBM software support representative.

   On distributed platforms, we can use the collector tool (collector.bat or collector.sh located in the bin directory) to gather trace information and other configuration information for the support team to diagnose the problem. The collector tool gathers dynamic cache service files and packages them into a JAR file. The IBM representative can specify when and where to send the JAR file.

   The IBM representative might ask you to complete a diagnostic trace. To enable tracing in the admin console, click Troubleshooting > Logs and trace > server_name > Diagnostic trace and specify Enable trace with the following specification. The IBM representative can tell you what trace spec to enter. Note that dynamic cache trace files can become large in a short period of time; we can limit the size of the trace file by starting the trace, immediately recreating the problem, and immediately stopping the trace.

   For current information available from IBM Support on known problems and their resolution, see the IBM Support page.

   For technical support on dynamic cache service, see the IBM Support page.

Troubleshooting tips for the dynamic cache service

 

Related tasks

Task overview: Using the dynamic cache service to improve performance

 

Related information

Cache monitor
Displaying cache information