Fix (APAR):  PM36464

Status:  Fix

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

CMVC Defect:  PM36464

Byte size of APAR:  499333

Date: 2011-04-28

Abstract:  The high availability plugin-cfg.xml generation service fails to start, and a NullPointerException error is displayed.

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

ERROR DESCRIPTION:                                              
As a WebSphere Virtual Enterprise process is starting, the      
following exception is logged:                                  
                                                                
HAManagedItem E   HAMI0014E: HAMItemMember:com.ibm.ws.          
odc.xd.HAPluginCfgGenerator_com.ibm.ws.odc.xd.                  
HAPluginCfgGeneratorInterface.....                              
java..lang.RuntimeException: java.lang.NullPointerException     

LOCAL FIX:                                                      
N/A                                                             

PROBLEM SUMMARY

USERS AFFECTED:
 WebSphere Virtual Enterprise users of the
high availability plugin-cfg.xml
generation service.

PROBLEM DESCRIPTION:
The high availability plugin-cfg.xml
generation service fails to start,
and a NullPointerException error is
displayed.

RECOMMENDATION:
None

As processes are starting, a timing window exists where the
high availability manager can attempt to activate or deactivate
the high availability plugin-cfg.xml generation service before
the service is fully initialized. As a result, a
NullPointerException error is displayed, and the
plugin-cfg.xml service is not activated.

PROBLEM CONCLUSION:                                             
The initialization of the high availability plugin-cfg.xml      
generation service was altered to not register as a high        
availability item until the service is fully initialized. This  
change prevents the high availability manager from attempting   
to activate or deactivate the service before it is completely   
initialized.                                                    
                                                                
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 <was_root>/updateinstaller/version.txt.

1) Copy 6.1.1.0-WS-WXD-IFPM36464.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-IFPM36464.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-IFPM36464.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: