APAR status
Closed as program error.
Error description
After Upgrading from WAS 5.0.2 to WAS 5.0.3 we encountered a
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Dynamic Cache users using the *
* do-not-consume property. *
****************************************************************
* PROBLEM DESCRIPTION: Fragment with the do-not-consume *
* property set behaves incorrectly when *
* using jstl imports or esi is enabled. *
* Fragment marked do-not-consume *
* appears twice on a cache hit. This *
* problem is caused by the additional *
* buffering that is done when using *
* jstl imports or when esi is enabled. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
do-not-consume property behaves incorrectly when using jstl
imports or esi is enabled. Fragment marked do-not-consume
appears twice on a cache hit
Problem conclusion
Modified how Dynamic Cache handles storing fragments that are
marked do-not-consume. This allows for different types of
buffering that occur when using jstl or esi to not affect how
the do-not-consume property behaves. Fragments in these
scenarios will no longer appear twice on a cache hit.
Temporary fix Comments
APAR information |
APAR number |
PQ88706 |
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-05-11 |
Closed date |
2004-08-23 |
Last modified date |
2004-08-23 |
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 |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|