PK27109: AFTER UPGRADE TO V6.0.2.11, WSVR0017E AND NULLPOINTEREXCEPTION PREVENT WEBSPHERE MQ RESOURCES BEING USED.

PK27109; 6.0.2.11: after upgrade to v6.0.2.11, wsvr0017e an nullpointerexception

APAR status

• Closed as program error.

Error description

• WebSphere application servers with WebSphere MQ resources
  defined may be unable to use those resources following an
  upgrade to WebSphere Application Server 6.0.2.11.
  Customers with WebSphere MQ V6.0.1.1 installed locally are
  unaffected by this problem.
  
  Environment:
    WebSphere Application Server v6.0.2.11
    WebSphere MQ v6
  
  After upgrading to WebSphere Application Server 6.0.2.11,
  exceptions occur on application server startup if JMS resources
  are defined on the system.
  
  The error prevents the WMQ connection factories from being bound
  into the JNDI namespace making these resources unavailable to
  applications.  Other symptoms include Listener Ports failing to
  start up because the JNDI name of the connection factory is not
  found.
  
  Exceptions similar to these would be seen in the SystemOut.log:
  ResourceMgrIm E   WSVR0017E: Error encountered binding the J2EE
  resource, myQCF, as
  jms/myQCF from
  file:/C:/WebSphere60/AppServer/profiles/AppSrv1/config/cells/myC
  ell/resources.xml
  java.lang.NullPointerException
  com.ibm.ws.runtime.component.binder.JMSBinder.getMapNameStyleCom
  patibleValue(JMSBinder.java:330)
  com.ibm.ws.runtime.component.binder.MQQueueConnectionFactoryBind
  er.getBindingObject(MQQueueConnectionFactoryBinder.java:154)
  com.ibm.ws.runtime.component.ResourceMgrImpl.bind(ResourceMgrImp
  l.java:322)
  com.ibm.ws.runtime.component.ResourceMgrImpl.installResourceProv
  ider(ResourceMgrImpl.java:1022)
  
  ContainerImpl E   WSVR0501E: Error creating component null class
  com.ibm.ws.runtime.component.ResourceMgrImpl
  com.ibm.ws.exception.RuntimeWarning:
  java.lang.NullPointerException
  
  com.ibm.ws.runtime.component.ResourceMgrImpl.installResourceProv
  ider(ResourceMgrImpl.java:1040)
  com.ibm.ws.runtime.component.ResourceMgrImpl.installResource(Res
  ourceMgrImpl.java:904)
  com.ibm.ws.runtime.component.ResourceMgrImpl.installResources(Re
  sourceMgrImpl.java:844)
  com.ibm.ws.runtime.component.ResourceMgrImpl.loadResources(Resou
  rceMgrImpl.java:673)
  
  MDBListenerIm W WMSG0017E: Unable to lookup JMS resources, JNDI
  lookup exception:
  IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
  MDBListenerIm W WMSG0019E: start MDB Listener myMDBListenerPort,
  
  JMSDestination jms/myQueueDestination :
  javax.naming.NameNotFoundException:
  Context: myCell/nodes/myNode/servers/server1, name: jms/myQCF:
  First component in name myQCF not found. Root exception is
  org.omg.CosNaming.NamingContextPackage.NotFound:
  IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
  .
  Fix is targeted for WebSphere Application Server fix pack
  6.0.2.13.
  .
  

Local fix

• Install WMQ APAR IY82794 which was first shipped in WMQ 6.0.1.1
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of WebSphere Application Server        *
  *                 6.0.2.11 uilizing WebSphere MQ JMS           *
  *                 Resources.                                   *
  *                                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Fix Pack 11 (V6.0.2.11) for WebSphere   *
  *                      Application Server introduced an        *
  *                      inter-product dependency with           *
  *                      WebSphere MQ in order to resolve a      *
  *                      problem with JMS MapMessages.           *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: Affected users should apply the fix.         *
  *                                                              *
  ****************************************************************
  Following the installation of Fix Pack 11 for WebSphere
  Application Server (V6.0.2.11), applications reliant on
  WebSphere MQ Queue Connection Factories, WebSphere MQ Topic
  Connection Factories, or WebSphere MQ Connection Factories can
  become non-functional. Exceptions during application server
  start indicate that the applications will be affected by this
  problem. Application servers accessing a local WebSphere MQ
  6.0.1.1 or WebSphere MQ Client at 6.0.1.1 are unaffected.
  
  Applications reliant on the following WebSphere MQ JMS resources
  can become non-functional:
  WebSphere MQ Queue Connection Factories
  WebSphere MQ Topic Connection Factories
  WebSphere MQ Connection Factories
  The exceptions that occur when starting the application server
  prevent the WebSphere MQ connection factory from being bound
  into the JNDI namespace.  Side-effects of this problem could
  include Listener Ports which fail to start up because the JNDI
  name of the connection factory is not found. Exceptions similar
  to the following would be seen in the SystemOut.log file:
  ResourceMgrIm E   WSVR0017E: Error encountered binding the J2EE
  resource
  

Problem conclusion

• The fix resolves the problem.
  

Temporary fix

• *********
                         * HIPER *
                         *********
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PK27107

• APAR is sysrouted TO one or more of the following:

  PK27389

Fix information

• Fixed component name

  PLAT MSG COM

• Fixed component ID

  620400101

Applicable component levels

• R100 PSY

     UP