Fixes are available
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Given a scenario in which a cluster is being stopped and started, the WorkLoad Management (WLM) Cluster MBean receives notifications when the members have completed their starts and stops. If when attempting to stop a cluster, instead of receiving the normal process.stopped notfications, the WLM Cluster MBean receives process.failed notifications for the cluster members, this can temporarily put the Cluster MBean in a state which can lead to problems. If there is an attempt to start the same cluster within 5 minutes after the process.failed notifications arrive it can lead to the following NullPointerException: [2/5/10 8:10:45:974 EST] 0000011b ClusterMgrNot 3 run exception java.security.PrivilegedActionException: java.lang.NullPointerException at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManager Impl.java:4238) at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextM anagerImpl.java:4281) at com.ibm.ws.management.wlm.ClusterMgrNotificationHandler.run(Clus terMgr.java:1363) Caused by: java.lang.NullPointerException at com.ibm.ws.management.wlm.Cluster.processStarted(Cluster.java:23 71) at com.ibm.ws.management.wlm.Cluster.handleNotification(Cluster.jav a:2299) at com.ibm.ws.management.wlm.ClusterMgrNotificationHandler.notifica tionReceived(ClusterMgr.java:1496) at com.ibm.ws.management.wlm.ClusterMgrNotificationHandler.access$1 00(ClusterMgr.java:1299) at com.ibm.ws.management.wlm.ClusterMgrNotificationHandler$1.run(Cl usterMgr.java:1354) at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManager Impl.java:4183) ... 2 more This in turn can lead to other problems as ClusterMBean will not notify anyone that the cluster has successfully started. If the next start of that cluster is more than 5 minutes after the process.failed notifications, the code will function normally and no exceptions would be seen.
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: Users of IBM WebSphere Application Server * * V6.1 and V7.0 running ripplestarts or many * * starts and stops of clusters * **************************************************************** * PROBLEM DESCRIPTION: WorkLoad Management (WLM) * * NullPointerException in Cluster * * MBean * **************************************************************** * RECOMMENDATION: * **************************************************************** Given a scenario in which a cluster is being stopped and started, the WLM Cluster MBean receives notifications when the members have completed their starts and stops. If when attempting to stop a cluster, instead of receiving the normal process.stopped notifications, the WLM Cluster MBean receives process.failed notifications for the cluster members, this can temporarily put the Cluster MBean in a state which can lead to problems. If there is an attempt to start the same cluster within 5 minutes after the process.failed notifications arrive it can lead to the following NullPointerException: Caused by: java.lang.NullPointerException at com.ibm.ws.management.wlm.Cluster.processStarted(Cluster.java:23 71)
Problem conclusion
The ClusterMBean code was rewritten to handle process.failed notifications properly with respect to the notification threads to avoid threading issues and subsequently the NullPointerException The fix for this APAR is currently targeted for inclusion in fix packs 6.1.0.33, 7.0.0.13. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM10161
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-03-17
Closed date
2010-04-13
Last modified date
2010-04-13
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
Document Information
Modified date:
25 October 2021