Technote

(FAQ)
Exceptions thrown inside JSP fragments are cached
Problem
If dynamic caching is enabled on your WebSphere Commerce store and a JSP fragment throws an exception, the exception message can end up cached. This will cause all subsequent requests to see the exception message.
Cause
If an exception is thrown anywhere during the request, WebSphere Commerce will set the request to uncachable. This is failing in the case where the request is for a JSP fragment.
Solution
Upgrade to WAS 6.0.2.17 and contact IBM Support for the APAR fix LI72065.
Cross Reference information
Segment Product Component Platform Version Edition
Commerce WebSphere Commerce Professional Edition Runtime AIX, i5/OS, Linux, Solaris, Windows 6.0, 6.0.0.1 Professional Edition
Commerce WebSphere Commerce Developer Enterprise Runtime Windows 6.0, 6.0.0.1 Enterprise
Commerce WebSphere Commerce Developer Professional Edition Runtime Windows 6.0, 6.0.0.1 Developer Professional Edition
Commerce WebSphere Commerce - Express Runtime i5/OS, Windows 6.0, 6.0.0.1 Express
Commerce WebSphere Commerce Developer Express Runtime Windows 6.0, 6.0.0.1 Developer Express
   

Document Information

Current web document: http://www.ibm.com/support/docview.wss?uid=swg21261169