Fix (APAR): PM47755 Status: Fix Release: 6.1.1.4,6.1.1.3,6.1.1.2,6.1.1 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: PK99664;PM04611;PM05220;PM06349;PM07037;PM08969;PM11582;PM11623;PM12939;PM18326;PM22866;PM25095;PM30114;PM31735;PM31801;PM33050;PM33283;PM36464;PM44418;PM46463 CMVC Defect: xxxxxx Byte size of APAR: 517671 Date: 2011-11-03 Abstract: Processes that host ODC plugin-cfg.xml generators incur frequent garbage collections resulting in elevated CPU utilization. Description/symptom of problem: PM47755 resolves the following problem: ERROR DESCRIPTION: The client's DMGR is running with no load or jobs and 10-20% CPU usage is displayed. The client enabled Allocation threshold tracing and we found all the large objects were from the following: JVMDUMP006I Processing dump event "allocation", detail "2139472 bytes Thread=Thread-154 (0B169DE0) Status=Running at java/lang/StringBuffer.ensureCapacityImpl(I)V (StringBuffer.java:3 at java/lang/StringBuffer.append(Ljava/lang/String;)Ljava/lang/Stri ng at com/ibm/ws/odc/nd/ODCPluginCfgGenerator.addRequestMetrics(Ljava/ la at com/ibm/ws/odc/nd/ODCPluginCfgGenerator.generatePluginCfg(Lcom/i bm at com/ibm/ws/odc/nd/ODCPluginCfgGenerator.handleEvents([Lcom/ibm/w ss at com/ibm/ws/odc/nd/ODCTreeImpl.commitTransaction(Lcom/ibm/wsspi/o dc LOCAL FIX: Setting cell prop ODCPluginCfgDisabled_ to true. This will disable the plugin-cfg.xml generation for that definition. Setting this must be sync'ed out to at least the process that is running the plugin generator. PROBLEM SUMMARY USERS AFFECTED: All users of WebSphere Virtual Enterprise that automatically generate a plugin-cfg.xml via On Demand Configuration (ODC) generators. PROBLEM DESCRIPTION: Processes that host ODC plugin-cfg.xml generators incur frequent garbage collections resulting in elevated CPU utilization. RECOMMENDATION: None ODC based plugin-cfg.xml generators rebuild the plugin-cfg.xml file contents in memory every time an ODC change event is received. The newly rebuilt contents are then compared to the last plugin-cfg.xml file that was output to determine if the contents have change and if so a new plugin-cfg.xml file is written to disk. There are many ODC change events that can be received which would in no way impact the contents of the plugin-cfg.xml but when received the contents are still unnecessarily rebuilt for comparison. The receipt of ODC change events that would not impact the contents of the plugin-cfg.xml can occur frequently enough that rebuilding the contents can raise garbage collection intervals resulting in higher cpu utilization. The high availability plugin-cfg.xml generator and the plugin-cfg.xml generation performed by On Demand Routers are both ODC based plugin-cfg.xml generators. PROBLEM CONCLUSION: ODC based plugin-cfg.xml generators have been altered to ignore receipt ODC change events that will not impact the contents of the generated plugin-cfg.xml. Therefore reducing the rebuild frequency of the plugin-cfg.xml contents and eliminating the overhead of unnecessarily performing this action. This fix will be included in the next available fix pack for WebSphere Virtual Enterprise. Directions to apply fix: Install Fix to: __ Application Server Nodes __ Deployment Manager Nodes _X_ Both NOTE: The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. Also, you should be logged in with the same authority level when unpacking a fix, fix pack or refresh pack. DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX. The Fix 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. Customers must be at V6.1.0.17 or newer of the Update Installer.?This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. 1) Copy 6.1.1.0-WS-WXD-IFPM47755.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 (6.1.1.0-WS-WXD-IFPM47755.pak 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. NOTE: 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.1.1.0-WS-WXD-IFPM47755.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: