Fix (APAR): PK15035 Status: Fix Release: 5.1.1.6,5.0.2.14,5.0.2.13,5.0.2.12 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: PK15035 Byte size of APAR: 44568 Date: 2005-11-11 Abstract: Memory leak in InvocationCache.(Replacement for PK12027 interim fix) Description/symptom of problem: After upgrading to WebSphere Application Server Fix Pack 5.1.1.6, 5.0.2.12, 5.0.2.13 or 5.0.2.14 and applying PK12027 interim fix, a memory leak has been found in Invocation Cache which leads to OutOfMemory situation. LOCAL FIX: LOCAL FIX 1: Temporary work around 1: Setting invocation cache size to 0 will disable invocation cache functionality and there will be no more caching of WebAppInvoker objects. This can be set as follows: (1) In the administrative console, click the application server. (2) Click Process Definition under Additional Properties. (3) Click the Java Virtual Machine under Additional Properties. (4) Add the following argument in the Generic JVM arguments: -DinvocationCacheSize=0 (5) Click Apply to ensure that the changes are saved. (6) Stop and restart the application server. LOCAL FIX 2: If invocation cache size can not be set to 0, this issue can be avoided by setting the minimum thread pool size the same as the maximum thread pool size and setting growable to false. To make these changes, perform the following: (1) In the administrative console, click the application server. (2) Click Web Container under Additional Properties. (3) Click Thread pool under Additional Properties. (4) Change Minimum size same as Maximum size. (5) UnCheck IsGrowable. (6) Click Apply to ensure that the changes are saved. (7) Stop and restart the application server. PROBLEM SUMMARY USERS AFFECTED: WebSphere Application Server users of version 5.0.2.12, 5.0.2.13, 5.0.2.14, 5.1.1.6 PROBLEM DESCRIPTION: After upgrading to WebSphere Application Server Fix Pack 5.1.1.6, 5.0.2.12, 5.0.2.13 or 5.0.2.14 and applying PK12027 interim fix, a memory leak has been found in Invocation Cache which leads to OutOfMemory situation. RECOMMENDATION: None PROBLEM CONCLUSION: This interim fix resolves the OutOfMemory in InvocationCache for levels 5.0.2.12, 5.0.2.13, 5.0.2.14 & 5.1.1.6.This will also resolve the NullPointerException caused due to the incomplete iFix PK12027 version 5.1.1.6. Please Note this is a replacement APAR only for PK12027 interim fix. The Cumulative fix pack which includes PK12027 need not apply this fix.Hence, this fix will not be made part of any cumulative fix pack. Directions to apply fix: Fix applies to Editions: Release: 5.0 5.1 X X Application Server (Express or BASE) X X Network Deployment (ND) Install Fix to: Method: X Application Server Nodes X Deployment Manager Nodes X 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: PK15035_5116_fix.jar to be applied on 5.1.1.X level (5.1.1.6) PK15035_50212_50213_fix.jar to be applied on 5.0.2.X level(5.0.2.12, 5.0.2.13, 5.0.2.14)