Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Troubleshooting
Dynamic caching in an application
WebSphere Commerce uses the JSTL (Java Server Tag Library) to create new JSP pages. This enables a Web developer to create a Java page without having to worry about the underlying code, while a Java developer can write the code simultaneously, or at a later period. Unfortunately, dynamic caching cannot execute the JSTL <c:import> tag on its own.
Pages are not being cached
Verify that the cachespec.xml file has been loaded into WebSphere Application Server. If the cachespec.xml is loaded, then the policies should be viewable from the Cache Monitor by clicking on the Cache Policies link on the side bar.

Troubleshooting: Pages are not being cached

Verify that the cachespec.xml file has been loaded into WebSphere Application Server. If the cachespec.xml is loaded, then the policies should be viewable from the Cache Monitor by clicking on the Cache Policies link on the side bar.

In addition the WebSphere Application Server SystemOut.log file will show a line similar to:


[6/6/03 21:21:12:635 EDT] 65c60609 ConfigManager I DYNA0047I:
Successfully loaded
   cache configuration file
D:\WebSphere\AppServer5\installedApps\buzz\WC_demo.ear\
   Stores.war\WEB-INF\cachespec.xml.

Log into the WebSphere Administrative Console to verify that dyancache is enabled by expanding the Applications menu, and selecting Enterprise Applications from the sub menu. Dynamic Cache Monitor should appear in the right pane.