Fix (APAR):  PK54884

Status:  Fix

Release:  6.0.2.1,6.0.2

Operating System:  AIX,HP-UX,Linux,Solaris,Windows,z/OS

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  23063

Date: 2007-10-31

Abstract:  The Placement controller may put too many DC instances on a given node.

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

ERROR DESCRIPTION:                                              
In a single cell topology using WebSphere XD, the APC controller
will place servers correctly at startup, but as these servers   
grow in heap size from their min heap to their max heap, the    
system memory can be exceeded and APC does not protect against  
that.  This takes down nodes in the production cell causing a   
lot of problems that are exposed to the end users.              

LOCAL FIX:                                                      
None                                                            

PROBLEM SUMMARY

USERS AFFECTED:
All users of WebSphere Application Server
also running WebSphere Extended Deployment.

PROBLEM DESCRIPTION:
The Placement controller may put too
many DC instances on a given node.

RECOMMENDATION:
None

Because of potential issues on certain operating systems, AIX
being one recently observed, with determining per process
memory utilizations, the Application Placement controller
would over provision DC instnaces on certain nodes, leading
to memory shortages.

PROBLEM CONCLUSION:                                             
A new custom property on the Application Placement controller   
config, useNodeFreeMemory, if set to true, will tell the        
Placement Controller to use node free memory instead of         
looking at the per DC instance memory used on a given node.     
This fix will be in the next 6.0.2.x fix pack                   
(yet to be announced), 6.1.0.1, and in IFIX form.               
Level 3 should be contacted before using this fix on Linux.     


Directions to apply fix:  
Install Fix to:
NOTE: Developers -  Place and X next to the proper installation method and remove this note
_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. 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.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.

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