Fix (APAR):  PK10456

Status:  Fix

Release:  5.1.1.5,5.0.2.12

Operating System:  AIX,HPUX,Linux,OS/400,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  PK10456

Byte size of APAR:  48301

Date: 2005-09-22

Abstract:  Memory Leak in FragmentComposer for applications with large servlet responses.  The servlet response is written to the cache buffer even in the case where the fragment is non-cacheable.

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

ERROR DESCRIPTION:                                              
Leak in FragmentComposer of Dynamic Cache.                      
Here is the snapshot.                                           
                                                                
1)568,697,232 [128] 9 com/ibm/ws/cache/servlet/FragmentComposer 
0x392f2a10                                                      
 379,130,184 [64] 4 com/ibm/ws/cache/servlet/CacheProxyResponse 
0x5ca32c18                                                      
 379,129,416 [72] 5 com/ibm/ws/cache/servlet/CacheProxyWriter   
0x5ca2d89                                                       
 189,564,664 [40] 3 com/ibm/ws/io/WSCharArrayWriter 0x5c0edc58  

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
Dynamic Cache users that have servlet
caching enabled and applications that
return large servlet responses.

PROBLEM DESCRIPTION:
Memory Leak in FragmentComposer for
applications with large servlet
responses.  The servlet response is
written to the cache buffer even in
the case where the fragment is
non-cacheable.

RECOMMENDATION:
None

There is a memory Leak in FragmentComposer for applications
with large servlet responses.

PROBLEM CONCLUSION:                                             
Disabled writing to the caching buffer for servlet responses    
that are not cacheable and have no parent fragments that have   
consume-subfragments set to true.                               
                                                                
The fix for this APAR is currently targeted for inclusion       
in 5.02.14, 5.1.1.8 and 6.0.2.3.                                
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: