Fix (APAR):  PK13653

Status:  Fix

Release:  6.0.2.3

Operating System:  AIX,HP-UX,Linux,Linux Red Hat - pSeries,Linux zSeries,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  PK13653

Byte size of APAR:  27094

Date: 2006-02-06

Abstract:  There is a problem in propagating the Notfications to an upstream server with RMIConnector.

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

ERROR DESCRIPTION:                                              
Notification issues with RMI Connector.                         
                                                                
Issues with RMI connector and Notifications handling, causes    
stop cluster action to fail.                                    
                                                                
FFDC error from clustermember/nodeagent.                        
Exception = java.lang.NullPointerException                      
Source = com.ibm.ejs.util.am._Alarm.run                         
probeid = 95                                                    
Stack Dump = java.lang.NullPointerException                     
 at                                                             
com.ibm.ws.management.connector.rmi.RMINotificationListenerAdapt
er.handl                                                        
eNotifications(RMINotificationListenerAdapter.java:44)          
 at                                                             
com.ibm.ws.management.event.PushRemoteSender.pushNotifications(P
ushRemot                                                        
eSender.java:56)                                                
 at                                                             
com.ibm.ws.management.event.AbstractPushRemoteSender.alarm(Abstr
actPushR                                                        
emoteSender.java:183)                                           
 at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:90)              
 at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1455) 

LOCAL FIX:                                                      
None.                                                           

PROBLEM SUMMARY

USERS AFFECTED:
Websphere Application Server users of
Version 6.

PROBLEM DESCRIPTION:
There is a problem in propagating the
Notfications to an upstream server with
RMIConnector.

RECOMMENDATION:
None

The administrative console shows the wrong status for a
cluster/server when the RMIConnector is used (that is, when
RMIConnector is chosen to be the default connector). The
Nodeagent process reports the following exception in the FFDC
logs:
Dump=java.lang.NullPointerException
at
com.ibm.ws.management.connector.rmi.
RMINotificationListenerAdapter.handleNotifications
RMINotificationListenerAdapter.java:44)
at

com.ibm.ws.management.event.PushRemoteSender.pushNotifications
(PushRemoteSender.java:56)

The cluster/server status does not get reflected due to missing
notifications.

PROBLEM CONCLUSION:                                             
Notification code has been altered to make it work with         
RMIConnector.                                                   
                                                                
The fix for this APAR is currently targeted for inclusion       
in fixpack 6.0.2.7.                                             
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: