Fix (APAR): PK32201 Status: Fix Release: 6.0.2.17,6.0.2.15 Operating System: AIX,HP-UX,Linux,Windows Supersedes Fixes: CMVC Defect: PK32201 Byte size of APAR: 49566 Date: 2007-04-13 Abstract: In the PUSH replication mode Dynacache sends large replication messages which frequently cause the Java Virtual Machiness in a clustered environment to exhaust their heaps, resulti Description/symptom of problem: PK32201 resolves the following problem: ERROR DESCRIPTION: In the PUSH replication mode WebSphere Application Server Dynacache sends replication messages that are large, which frequently causes the Java Virtual Machines in a clustered environment to exhaust their heaps, resulting in Out Of Memory errors and heap dumps. The fix allows the user to specify a few custom properties enable Dynacache to chunk these messages thereby sending only a few cache entries at a time in a message, resulting in smaller objects and helping these heap exhaustion issues. LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: WebSphere Application Server users of dynamic cache who configure cache replication in PUSH mode. PROBLEM DESCRIPTION: In the PUSH replication mode Dynacache sends large replication messages which frequently cause the Java Virtual Machiness in a clustered environment to exhaust their heaps, resulting in OutOfMemory errors and heap dumps. RECOMMENDATION: None In the PUSH replication mode Application Server's, Dynacache service sends replication messages that are large, which frequently causes the servers in a clustered environment to exhaust their java virtual machine heaps, resulting in OutOfMemory errors and heap dumps. PK32201 relieves this issue by allowing the user to control the size (in terms of number of cache entries) of the sent messages. PROBLEM CONCLUSION: The batch size of the replication data can now be configured using the following custom properties: com.ibm.ws.cache.CacheConfig.cachePercentageWindow: Specifies a limit on the number of cache entries sent by the Data Replication Service in terms of the percentage of total cache in memory. Default value: 2% of the no. of entries in the cache Scope: configurable per cache instance com.ibm.ws.cache.CacheConfig.cacheEntryWindow: Specifies a limit on the total number of cache entires sent by the Datat Replication Service in terms of number of entries. Default value: 50 entries Scope: configurable per cache instance com.ibm.ws.CacheConfig.batchUpdateMilliseconds: Specifies a batch update frequency in terms of milliseconds. Setting this property will result in Dynacache processing updates more frequently, and thus reducing the payload size. Default Value: 1000 ms (1 s) The fix for this APAR is currently targeted for inclusion in cumulative fix 5.1.1.14, and fixpacks 6.0.2.19, and 6.1.0.7. 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 6.0 __ Application Server (Express or BASE) X Network Deployment (ND) __ WebSphere Business Integration Server Foundation (WBISF) __ Edge Components Developer __ Extended Deployment (XD) Install Fix to: Method: X 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. * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 For detailed instructions to Extract the Update Installer see the following Technote: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy (WAS 6.0.2.15) 6.0.2.15-17-WS-WASND-IFPK32201.pak OR (WAS 6.0.2.17) 6.0.2.17-WS-WASND-IFPK32201.pak 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.pak file which was copied in the maintenance directory). 7) Install the maintenance package. 8) Restart WebSphere NOTE: Please apply 6.0.2.15-17-WS-WASND-IFPK32201.pak if the base WebSphere Application Server version is 6.0.2.15. Please apply 6.0.2.17-WS-WASND-IFPK32201.pak if the base WebSphere Application Server version is 6.0.2.17. 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 (6.0.2.15-17-WS-WASND-IFPK32201.pak) or (6.0.2.17-WS-WASND-IFPK32201.pak). 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: