10.5.6 Troubleshooting the dynamic cache service

 

+

Search Tips   |   Advanced Search

 

  1. Use the Cache monitor to test.

  2. Verify cachespec.xml file.

  3. Review the JVM logs for your appserver. Messages prefaced with DYNA result from dynamic cache service operations.

    • View the JVM logs for your appserver. Each server has its own JVM log file. For example, if your server is named Web1, the JVM log is located in...

        <install_root>/logs/Web1/

      Alternatively, use the Administrative Console to review the JVM logs, click...

        Troubleshooting | Logs and Trace | <AppServer_Name> | JVM Logs | Runtime tab | View

    • Find any messages prefaced with DYNA in the JVM logs, and write down the message IDs. A sample message having the message ID DYNA0030E follows:

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

    • Find the message for each message ID in the WAS InfoCenter. In the InfoCenter navigation tree, click <product_name> -> Reference -> Troubleshooter -> Messages -> DYNA to view dynamic cache service messages.

    • Try the solutions stated under User Response in the DYNA messages.

    • Enable tracing on the appserver for com.ibm.ws.cache.*. To enable it, click Troubleshooting -> Logs and Trace -> <AppServer_Name> -> Diagnostic Trace in the WAS console. Click the Configuration tab, click the Enable Log checkbox and click OK.

      Click...

        Troubleshooting | Logs and Trace | <AppServer_Name> | Change Log Detail Levels | Configuration tab

      ...and add the trace string...

        com.ibm.ws.cache.*=all

      Separate entries with a colon (:).

      Note that *=info is the default value, so we recommend keeping it in the configuration.

      If you experience problems with cache replication, then enable the trace for com.ibm.ws.drs.*.

      We need to restart the server and monitor the trace file.

Next