PK69053: NULLPOINTEREXCEPTION IS THROWN DURING APPLICATION SERVER START UP.

Fixes are available

APAR status

Closed as program error.

Error description

The following error was logged to the JVM logs of an
application server on startup when using WebSphere MQ as a
messaging provider:

[6/18/08 17:41:13:941 EDT] 0000000a ContainerImpl E
  WSVR0501E: Error creating component
                      com.ibm.ejs.jms.JMSRegistration@1f72e08e
java.lang.ExceptionInInitializerError
 at com.ibm.ejs.jms.JMSRegistration.start
                                    (JMSRegistration.java:527)
 at com.ibm.ws.runtime.component.ContainerImpl.
                       startComponents(ContainerImpl.java:977)
 at com.ibm.ws.runtime.component.ContainerImpl.start
                                      (ContainerImpl.java:673)
 at com.ibm.ws.runtime.component.ServerImpl.start
                                         (ServerImpl.java:526)
 at com.ibm.ws.runtime.WsServerImpl.bootServerContainer
                                       (WsServerImpl.java:192)
 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)
...
Caused by: java.lang.NullPointerException
 at org.eclipse.osgi.framework.internal.core.BundleLoader.
                         findLocalClass(BundleLoader.java:334)
 at org.eclipse.osgi.framework.internal.core.
    SingleSourcePackage.loadClass(SingleSourcePackage.java:37)
 at org.eclipse.osgi.framework.internal.core.BundleLoader.
                              findClass(BundleLoader.java:374)
 at org.eclipse.osgi.framework.internal.core.BundleLoader.
                              findClass(BundleLoader.java:347)
 at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.
                         loadClass(DefaultClassLoader.java:83)

Local fix

Add diagnostics and handle the NPE more appropriatly.

Problem summary

****************************************************************
* USERS AFFECTED:  Users WebSphere Application Server V6.1     *
*                  using WebSphere MQ as a messaging provider  *
****************************************************************
* PROBLEM DESCRIPTION: When a class called                     *
*                      'com.ibm.mq.MQEnvironment' exists in    *
*                      the classpath of an application         *
*                      server, inside a jar which is not       *
*                      part of the WebSphere MQ JMS client     *
*                      installation pointed to by              *
*                      MQ_INSTALL_ROOT, a                      *
*                      NullPointerException can occur.         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
WebSphere Application Server relies upon a single instance
of class called com.ibm.mq.MQEnvironment existing in the
classpath of the application server, and that this class is
inside a WebSphere MQ JMS client installation.

In this case, a second instance of the class existed in
another jar in the classpath of the application server.
This resulted in a NullPointerException because the
application server expected the jar in which the class is
contained to include WebSphere MQ JMS client version
information.

Problem conclusion

This APAR makes the WebSphere Application Server code more
defensive, to improve the diagnostic information output when
the com.ibm.mq.MQEnvironment class is loaded from a jar that
is not part of a WebSphere MQ JMS client installation.

The duplicate class must still be eliminated from the classpath
of the application server to allow WebSphere MQ JNDI resources
to be used by applications.

If this same issue occurs with the APAR applied, a FFDC with
probeid "302" or "303" will be dumped from
com.ibm.ejs.jms.MA88Install, and message WMSG1605E will be
logged to the JVM logs of the application server.
An application attempting to access a WebSphere MQ JNDI
resource after the server has started will be thrown an
javax.naming.NamingException containing message WMSG2001E.

The fix for this APAR is currently targeted for inclusion in
fixpack 6.1.0.23. 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
PK69053
Reported component name
PLAT MSG COM
Reported component ID
620400101
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-07-15
Closed date
2008-09-12
Last modified date
2008-09-12

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
PLAT MSG COM
Fixed component ID
620600101

Applicable component levels

R200 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"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:
29 December 2021

Tips

PK69053: NULLPOINTEREXCEPTION IS THROWN DURING APPLICATION SERVER START UP.

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

R200 PSY

Document Information

Share your feedback

Need support?