Fix (APAR):  PK40614

Status:  Fix

Release:  6.0.2

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

Supersedes Fixes:  

CMVC Defect:  PK40614

Byte size of APAR:  205828

Date: 2007-04-03

Abstract:  The Autonomic Placement Controller does not stop idle instances immediately.

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

ERROR DESCRIPTION:                                              
The lazy start controller does not shutdown idle instances after
given time. The administrative console and help documentation   
states that idle instances will be shutdown after periods of    
inactivity.                                                     
It is extremely important in shared environments that the unused
servers are shutdown if not being used .                        
Have tried multiple timeout values and all fail to shutdown idle
instances.                                                      

LOCAL FIX:                                                      
No work-around available.                                       

PROBLEM SUMMARY

USERS AFFECTED:
All users of WebSphere Extended Deployment
who use Dynamic Clusters in automatic mode.

PROBLEM DESCRIPTION:
The Autonomic Placement Controller does
not stop idle instances immediately.

RECOMMENDATION:
None

The Application Placement controller is responsible for
starting and stopping dynamic cluster members based on the
incoming traffic to the website. The customer can configure
dynamic clusters to be totally stopped during periods of
inactivity. By the current design of the application placement
controller, dynamic cluster instances are not stopped unless
the controller percieves a condition of memory contention.
This can be undesirable for customers. This fix addresses this
problem by allowing customers to force the placement controller
to stop idle dynamic cluster members immediately after the
idle period expires.

PROBLEM CONCLUSION:                                             
This fix causes the application placement controller to stop    
idle dynamic cluster members immediately after the period of    
inactivity. In order to configure this behavior, the system     
administrator needs to configure a boolean custom property      
on the dynamic cluster(s) that he desires this behavior for,    
having the name "proactiveIdleStop" and value "true". This      
fix will be made available for versions 6.0.2 (product code     
XD) and 6.0.2 over Network Deployment 6.1(product code WXD)     


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: