Fix (APAR):  PK34666

Status:  Fix

Release:  6.0.2

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

Supersedes Fixes:  

CMVC Defect:  PK34666

Byte size of APAR:  11905

Date: 2006-11-22

Abstract:  The excessive memory usage policy was unable to detect an excessive memory usage condition when the server memory utilization violated the configured policy.

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

ERROR DESCRIPTION:                                              
The health monitor is configured to recycle the server if more  
than 50% of the heap is exceeded for a time period over one     
minute.  When the memory threshold had exceeded the health      
manager is not cycling servers.                                 

LOCAL FIX:                                                      
none                                                            

PROBLEM SUMMARY

USERS AFFECTED:
All users of WebSphere Extended Deployment
version 6.0.2 using Health monitoring
policies to detect excessive memory usage.

PROBLEM DESCRIPTION:
The excessive memory usage policy was
unable to detect an excessive memory
usage condition when the server
memory utilization violated the
configured policy.

RECOMMENDATION:
None

A bug in the excessive memory subsystem was causing the
recorded readings of each servers memory utilization to get
reset every control cycle period. Due to this, any history
information maintained by the memory sensor was getting
erased and an excessive memory condition was never being
triggered. This problem is especially undesirable and readily
noticed when using a shorted control cycle interval, that is
shorter than the default 5 minute cycle.

PROBLEM CONCLUSION:                                             
This fix corrects the behaviour that is caused by this bug and  
allows the excessive memory utilization condition to fire       
as desired. This fix can be installed on top of WebSphere       
Extended Deployment v6.0.2 and v6.0.2 over WebSphere            
Application Server version 6.1.0.x.                             

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