Fix (APAR): PM49326 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;PM47755 CMVC Defect: xxxxxx Byte size of APAR: 517756 Date: 2011-11-03 Abstract: WebSphere Virtual Enterprise processes display elevated CPU usage and can be slow to respond. Description/symptom of problem: PM49326 resolves the following problem: ERROR DESCRIPTION: Reduces ODC change activity caused by excessive nodedetect calculations LOCAL FIX: n/a PROBLEM SUMMARY USERS AFFECTED: All users of WebSphere Virtual Enterprise. PROBLEM DESCRIPTION: WebSphere Virtual Enterprise processes display elevated CPU usage and can be slow to respond. RECOMMENDATION: None The On Demand Configuration (ODC) component registers as a NodeDetect listener in all processes and does not differentiate what node a NodeDetect event applies to. Therefore for any given NodeDetect change every process will respond by updating it's local ODC tree and then broadcast the corresponding ODC change event for consumption by all other remote processes. This results in redundant ODC notifications that scale with the size of the environment. The redundant ODC notifications are compounded by the frequency at which some NodeDetect values are updated. The net result of this is raised demand for the ODC tree lock and can cause lock contention in processes that already have large demands on the tree lock. The ODC tree lock contention will surface in the form of cpu spikes and will impact the responsiveness of the effected process. Deployment Manager and On Demand Router processes are most susceptible to this as well as processes that have a defined trace specification which causes the ODC tree to be written to disk. PROBLEM CONCLUSION: ODC has been altered to only register as a NodeDetect listener within Deployment Manager and NodeAgent processes. Also ODC will now derive ownership for NodeDetect changes so that only the process for which the NodeDetect change applies will update the ODC tree and broadcast the corresponding ODC change event. These changes remove the redundant ODC notifications and therefore alleviate the demand for the ODC tree lock which was previously incurred. 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-IFPM49326.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-IFPM49326.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-IFPM49326.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: