+

Search Tips   |   Advanced Search

Troubleshoot the dynamic cache service

  1. Review the appserver logs in subdirectory...

      profile_home/logs/servername

    From console...

      Troubleshooting | Logs and trace | server | JVM logs | Runtime | View

  2. Find any messages prefaced with DYNA in the log we are viewing, and write down the message IDs.

    For example...

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

  3. Find the message for each message ID in the information center for WebSphere Application Server.

    product_name | Reference | Troubleshooter | Messages | DYNA

  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.

  6. Use the cache monitor to determine whether the dynamic cache service is functioning as expected.

    The cache monitor is an installable web application that displays simple cache statistics, cache entries, and cache policy information.

  7. 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 to gather dynamic cache service files and package them into a JAR file. The IBM representative can specify when and where to send the JAR file.

To enable tracing in the administrative console...

The IBM representative can tell us what trace specification 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 re-creating the problem, and immediately stopping the trace.


Subtopics


Related:

  • Cache monitor
  • Displaying cache information
  • Task overview: Using the dynamic cache service to improve performance
  • View JVM logs
  • http://www.ibm.com/support/search.wss?rs=180&tc=SSEQTP&tc1=SSCVRZY