APAR status
Closed as program error.
Error description
If the JSP is cached by DynaCache, changing the source of that
JSP do not trigger the invalidation of that JSP cached entry
although the JS source is re-compiled.
Local fix
no work around
Problem summary
****************************************************************
* USERS AFFECTED: Any user on WebSphere Application Server *
* v5.0.2 who uses WebSphere Dynamic Cache to *
* cache JSP content and manually updates *
* JSPs after the application has been started. *
****************************************************************
* PROBLEM DESCRIPTION: JSP cached entries are not *
* invalidated after JSP recompile *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Once a JSP has been compiled and accessed, and content has
been cached, a manual modification to the JSP will correctly
cause a recompile but any cached entries for that JSP are not
invalidated.
Problem conclusion
The above is incorrect behavior. After a JSP is recompiled,
all cached entries for that JSP must be invalidated to allow
the newly recompiled JSP to execute and regenerate cachable
content.
Temporary fix Comments
APAR information |
APAR number |
PQ90959 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-07-04 |
Closed date |
2004-07-14 |
Last modified date |
2004-07-14 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
|