Fix (APAR): PK10276 Status: Fix Release: 5.1.1.7,5.1.1.6,5.1.1.5,5.0.2.12,5.0.2.11,5.0.2.10 Operating System: AIX,HP-UX,Linux,OS/400,Solaris,Windows Supersedes Fixes: CMVC Defect: PK10276 Byte size of APAR: 214033 Date: 2005-11-23 Abstract: The Dynamic Cache's Push-Pull table is growing too big because the table is not being cleaned up in two cases. Description/symptom of problem: PK10276 resolves the following problem: ERROR DESCRIPTION: Dynacache has two spots leading to unrestricted growth in the internal push-pull table. LOCAL FIX: none PROBLEM SUMMARY USERS AFFECTED: WebSphere Application Server users who use the distributed replication service PUSH-PULL mode. PROBLEM DESCRIPTION: The Dynamic Cache's Push-Pull table is growing too big because the table is not being cleaned up in two cases. RECOMMENDATION: None The Dynamic Cache's Push-Pull table is not being cleaned up in the following cases when running Push-Pull mode: 1. After fetching the cache entry from the peer server, the cache id is not removed from the Push-Pull table. 2. When performing the dependency id invalidation, the cache ids associated with dependency id in the memory are not removed from the Push-Pull table. PROBLEM CONCLUSION: This fixes the memory leak in Dynamic cache caused by DRS Push-Pull table not being cleaned up. The fix for this APAR is currently targeted for inclusion in 5.02.14, 5.1.1.8 and 6.0.2.5. 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: The prerequisite APARs needed before installing PK03168 on WAS 5.0.2.10 are: 1. PK00682 (PK00682_ifix_v5_0210.jar) The prerequisite APARs needed before installing PK10276 (PK10276_IFix_v5_0210_11.jar) on WAS 5.0.2.10 or 5.0.2.11 are: 1. PK03168 (PK00682_ifix_v5_029_10.jar) 2. PK07880 (PK07880_ifix_v5_029_11.jar) 3. PK07544 (PK07544_efix.jar) 4. PK11928 (PK11928_ifix-502.jar) The prerequisite APARs needed before installing PK10276 (PK10276_IFix_v5_0212.jar) on WAS 5.0.2.12 are: 1. PK07880 (PK07880_ifix_v5_0212.jar) 2. PK07544 (PK07544_efix.jar) 3. PK11928 (PK11928_ifix-502.jar) The prerequisite APARs needed before installing PK10276 (PK10276_IFix_v5_115_6.jar) on WAS 5.1.1.5 or 5.1.1.6 are: 1. PK07880 (PK07880_ifix_v5_115_6.jar) 2. PK11928 (PK11928_ifix-511.jar) The prerequisite APARs needed before installing PK10276 (PK10276_IFix_v5_117.jar) on WAS 5.1.1.7 are: 1. PK11928 (PK11928_ifix-511.jar)