PK88364; 6.1.0.25: NullPointerException seen in ffdc log

Download Description

PK88364 resolves the following problem:

ERROR DESCRIPTION:
NullPointerException in
ws.management.AdminServiceImpl.readMBeanInvokeFilter

This causes no functional impact.

LOCAL FIX:

PROBLEM SUMMARY
The ffdc was being unnecessarily invoked.

USERS AFFECTED:
All users of IBM WebSphere Application Server who start an application server may see extraneous FFDC but there is no functional impact.

PROBLEM DESCRIPTION:
Extraneous NullPointerException appears in ffdc logs directory

RECOMMENDATION:
None

One of FFDC logs file contains:
-----Start of DE processing----- = [6/5/09 11:50:39:812 CDT] ,
key = java.lang.NullPointerException
com.ibm.ws.management.AdminServiceImpl.readMBeanInvokeFilter
2941
Exception = java.lang.NullPointerException
Source =
com.ibm.ws.management.AdminServiceImpl.readMBeanInvokeFilter
probeid = 2941
Stack Dump = java.lang.NullPointerException
at
com.ibm.ws.management.AdminServiceImpl.readMBeanInvokeFilter(Adm
inServiceImpl.java:2909)
at
com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImp
l.java:1988)
at
com.ibm.ws.management.AdminServiceImpl.access$400(AdminServiceIm
pl.java:120)
at
com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.ja
va:1114)
at
java.security.AccessController.doPrivileged(AccessController.jav
a:246)
at
com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon
troller.java:125)
at
com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.j
ava:1030)
at
com.ibm.ws.management.status.StatusCacheClient.invoke(StatusCach
eClient.java:232)
at
com.ibm.ws.management.status.StatusCacheClient.requestReport(Sta
tusCacheClient.java:114)
at
com.ibm.ws.management.status.StatusCacheClient.<init>(StatusCach
eClient.java:79)
at
com.ibm.ws.management.status.StatusCacheFactory.getStatusCacheCl
ient(StatusCacheFactory.java:92)
at
com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.j
ava:539)
at
com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(C
ontainerImpl.java:1338)
at
com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(
ContainerImpl.java:1171)
at
com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.ja
va:356)
at
com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl
.java:178)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:140)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:461)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
Impl.java:79)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
AccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at
com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:18
3)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:90)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:72)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Platfo
rmActivator.java:78)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.run
Application(EclipseAppLauncher.java:92)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.sta
rt(EclipseAppLauncher.java:68)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStart
er.java:400)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStart
er.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
Impl.java:79)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
AccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at
com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLaunche
r.java:329)
at
com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:92
)

PROBLEM CONCLUSION:
The extraneous FFDC was removed.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.0.2.37, 6.1.0.27 and 7.0.0.7. Please refer to the
recommended updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980