Fix (APAR):  PK22899

Status:  Fix

Release:  5.0.2.14

Operating System:  AIX,HP-UX,Linux,Linux pSeries,Linux Red Hat - pSeries,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  PK22899

Byte size of APAR:  20052

Date: 2006-04-24

Abstract:  Duplicate content is given on a cache hit when a parent servlet buffers its child includes.

Description/symptom of problem:  
PK22899 resolves the following problem:

ERROR DESCRIPTION:                                              
After upgrading the Websphere to 5.0.2.14, enabling dynacache to
cache fragemnts with WCM generated IllegalStateException. APAR  
PK12081                                                         
resolves this exception but it exposed another issue with       
fragment caching, New problem is that fragments are cache twice 
and hence when customer hits refresh or served from cache       
duplicate fragments are rendered to client.                     

LOCAL FIX:                                                      
none                                                            

PROBLEM SUMMARY

USERS AFFECTED:
All users who buffer included JSPs at the
parent, such as WCM

PROBLEM DESCRIPTION:
Duplicate content is given on a cache
hit when a parent servlet buffers its
child includes.

RECOMMENDATION:
None

Dynacache expects all included jsps to be flushed on
conclusion, and when these includes are buffered by their
consuming parent, dynacache caches twice; once on the jsp
include flush, and once on the parent flush. This situation
produces duplicate content.

PROBLEM CONCLUSION:                                             
A custom attribute, discardJSPContent, has been added to        
eliminate the duplicate content on cache hits. It can be        
utilized like in the following example:                         
                                                                
<% request.setAttribute("discardJSPContent", "true"); %>        
<jsp:include page="DiscardB1.jsp" flush="true" />               
<% request.setAttribute("discardJSPContent", "false"); %>       
                                                                
Note that this attribute must be used to bracket every include  
on the page--a user cannot selectively discard jsp includes     
in a parent.                                                    
                                                                
The fix for this APAR is currently targeted for inclusion       
in cumulative fixes 5.02.17 and 5.1.1.11 and fixpack 6.0.2.11.  
Please refer to the recommended updates page for delivery       
information:                                                    
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   
                                                                

Directions to apply fix:  NOTE: Choose the:
1) Release the fix applies to
2) The Editions that apply
3) Delete the Editions & Methods that do not apply and this Note

Fix applies to Editions:
Release:
5.0  5.1
___  ___ Application Server (Express or BASE)
___      Enterprise Edition (DD)
___  ___ Network Deployment (ND)
___  ___ Edge Components
___  ___ Developers Edition
___  ___ Tools
     ___ WebSphere Business Integration Server Foundation (WBISF)

Install Fix to:
Method:
__ Application Server Nodes
__ Deployment Manager Nodes
__ Both

NOTE:
The user must:
* Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* Be logged in with the same authority level when unpacking a fix, fix pack or refresh pack.

The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

The Update Installer for V5.0 does not have a maintenance directory.
It uses fixpacks and fixes as the location of the unpacked files.

1) Copy PKxxxxx.jar file directly to the maintenance directory

2) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to.

3) Launch Update Installer

4) Enter the installation location of the WebSphere product you want to update.

5) Select the "Install maintenance package" operation.

6) Enter the file name of the maintenance package to install (PKxxxxx.jar file which was copied in the maintenance directory).
The V5.0 and V5.1 fix packs and fixes are unpacked as .jar files and should be unpacked into fixpacks or fixes directory.

7) Install the maintenance package.

8) Restart WebSphere

Directions to remove fix:  NOTE:
* The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED
* DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED
* YOU MAY REAPPLY ANY REMOVED FIX

Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.

1) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against.

2) Start Update Installer

3) Enter the installation location of the WebSphere product you want to remove the fix.

4) Select  "Uninstall maintenance package" operation.

5) Enter the file name of the maintenance package to uninstall (PKxxxxx.jar).

6) UnInstall maintenance package.

7) Restart WebSphere

Directions to re-apply fix:  1) Shutdown WebSphere.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere.

Additional Information: