PK08245: NULLPOINTEREXCEPTION THROWN DURING WLMSERVLETLISTENER HANDLENOTIFICATION.

APAR status
Closed as program error.

Error description
NullPointerException thrown during WLMServletListener
handleNotification.

The stack trace for NPE.

[5/27/05 16:12:13:177 EST]  1a7a517 NotificationD W ADME0006W:
An
exception occurred sending notification
javax.management.Notification[source=WebSphere:platform=common,c
ell=cols
afNetwork,version=5.0,name=Discovery,mbeanIdentifier=Discovery,t
ype=Disc
overy,node=colsafManager,process=dmgr] to ListenerInfo:
[listener=com.ibm.ws.cluster.control.ClusterDescriptionListener@
1b57890;
ntfyInfo=NotificationInfo:
[name=WebSphere:*,type=Discovery;filter=javax.management.Notific
ationFil
terSupport@1dfe1a];handback=3]: java.lang.NullPointerException
 at
com.ibm.ws.cluster.control.ClusterDescriptionListener.handleNoti
fication
(Unknown Source)
 at
com.ibm.ws.management.event.ListenerInfo.handleNotification(List
enerInfo
.java:67)

This caused by  an MBean that does not have a type in
the type field:

[6/28/05 10:42:48:667 EST]   a53092 WLMServletLis d mBeanOName

NewAccessControlService:name=manager,version=05.04.0001,instance
=2005062
NewAccessControlService:name=manager,version=05.04.0001,instance
=2005062
81041320464,uniqueid=2
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of        *
*                 WorkloadManagement (WLM), or Clustering      *
****************************************************************
* PROBLEM DESCRIPTION: A NullPointerException is thrown from   *
*                      the WLMSservletListener during a        *
*                      handle notification for MBeans that     *
*                      have a NULL type.                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A null check was not made in the WLMServletListener, such
that during a handle notification when an MBean had a
null type, we used the type field, which caused the
NullPointerException to be thrown. This exception was printed,
but the exception itself was caught and is begnin (that is, it
does not affect the runtime system in any way).
Problem conclusion
A null check is now made, so a NullPointerException will not be
generated under these circumstances

The fix for this APAR is currently included in fixpack for
WebSphere Business Integration, release 5.1.1, cumulative fix 3
Temporary fix Comments
APAR information
APAR number PK08245
Reported component name WAS NETWRK DEPL
Reported component ID 5630A3601
Reported release 00S
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2005-06-30
Closed date 2005-09-13
Last modified date 2005-09-13

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
WLM          

Publications Referenced

Fix information
Fixed component name WAS ENTERPRISE
Fixed component ID 5630A3700

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Enterprise Edition (EE)
Operating system(s):
Software version: 00S
Software edition:
Reference #: PK08245
IBM Group: Software Group
Modified date: Sep 13, 2005