PM10161: WLM NULLPOINTER IN CLUSTER MBEAN

Fixes are available

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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PM10161: WLM NULLPOINTER IN CLUSTER MBEAN

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?