Fix (APAR):  PK25600

Status:  Fix

Release:  6.0.2.9,6.0.2.8,6.0.2.7,6.0.2.6,6.0.2.5,6.0.2.11

Operating System:  AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows,z/OS

Supersedes Fixes:  

CMVC Defect:  369347

Byte size of APAR:  31581

Date: 2006-07-25

Abstract:  Out of Memory exceptions causing crashes of Deployment Manager

Description/symptom of problem:  
PK25600 resolves the following problem:

ERROR DESCRIPTION:                                              
6.0.2 and 6.1 Deployment Managers with 5.x nodes on them can    
experience out of memory errors in larger environments due to   
interop code which handles the translation of cluster data      
between 6.x versions and 5.x versions.  This interop code was   
not designed with large scale topologies in mind, so            
improvements were needed in handling only the needed data and   
notifications instead of all data and notifications.            

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
Webpshere Application Server version 6
users with large version 6 topologies
and/or users running version 5 and
version 6 mixed node clusters.

PROBLEM DESCRIPTION:
Out of Memory exceptions causing
crashes of Deployment Manager

RECOMMENDATION:
None

In an mixed version 5 and version 6 node topology, the dmgr
registers to the bulletin board on behalf of all version 5
members, and there is code which translates all of the
version 5 descriptions to version 6 and vice versa. In a
reasonably sized cell this extra work can cause the deployment
manager to crash due to out of memory errors because of the
extra work processing the large numbers of notifications
passed around because the cell is mixed.

PROBLEM CONCLUSION:                                             
Optimization improvements were backported to version 6.0.2      
from version 6.1 for the WLM SleeperThreadPool for processing   
the notifications, and further improvements were made on both   
version 6.0.2 and version 6.1 to the interoperabiltiy code to   
limit the scope of the notifications it registers for, which    
eliminates a vast percentage of unneeded notifications from     
being sent around the cell.                                     
                                                                
The fix for this APAR is currently targeted for inclusion       
in fixpack 6.0.2.13 and 6.1.0.1.                                
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)
__ Network Deployment (ND)
__ WebSphere Business Integration Server Foundation (WBISF)
__ Edge Components
__ Developer
__ Extended Deployment (XD)

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.
* 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 <was_root>/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 PKxxxxx.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

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.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: