PQ95673: DO-NOT-CONSUME PROPERTY FOR NON-CACHEABLE FRAGMENTS

 Fixes are available

PQ95673; 5.0.2.8: Un-cacheable fragment can not be marked do-not-consume
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for AIX platforms
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
6.0.0.2: WebSphere Application Server Version 6.0.0 Fix Pack 2
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for HP-UX platforms
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for OS/400 platforms
5.1.1.6: WebSphere Application Server Version 5.1.1 Cumulative Fix 6
5.1.1.7: WebSphere Application Server Version 5.1.1 Cumulative Fix 7
5.1.1.4: WebSphere Application Server Version 5.1.1 Cumulative Fix 4
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for Solaris platforms
6.0.0.3: WebSphere Application Server V6.0.0 Fix Pack 3
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for Windows platforms
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for Linux platforms
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux
6.0.1.2: WebSphere Application Server Version 6.0.1 Fix Pack 2



APAR status
Closed as program error.

Error description
For a non-cacheable fragment to be marked do-not-consume a
user currently has to create a cache policy for this fragment
with a timeout of 1. This fix will allow a user to set the
do-not-consume property without creating a cache policy for
the fragment.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Dynamic Cache users using the                *
*                 do-not-consume property for an               *
*                 un-cacheable fragment                        *
****************************************************************
* PROBLEM DESCRIPTION: The do-not-consume property can not     *
*                      be set on an un-cacheable fragment.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The do-not-consume property can not be set on an un-cacheable
fragment.  To mark mark a fragment do-not-consume the user has
to create a cache policy for that fragment and set the
do-not-consume property to true.  However, if the fragment
is not cacheable the only option is to also set the timeout to
1.  In some scenarios caching the fragment for 1 second is not
valid.
Problem conclusion
Modified API to allow users to set the do-not-consume property
on a fragment without creating a cache policy.
Temporary fix Comments
APAR information
APAR number PQ95673
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-10-13
Closed date 2004-10-28
Last modified date 2004-10-28

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
DYNACACH          

Publications Referenced

Fix information

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


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ95673
IBM Group: Software Group
Modified date: Oct 28, 2004