PQ98520: NULL IS PICKED UP FOR THE VALUE OF QUEUE MANAGER NAME IF IT IS NOT SPECIFIED FOR THE MQ QUEUE CONNECTION FACTORY FOR WEBSPHERE.

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Currently if the 'queue manager name' is not specified for the
MQ Queue Connection Factory then a null value is picked up. This
apar addresses this so that the default queue manager name on
the system would be picked up instead of null.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: WebSphere Application Server for z/OS   *
*                      is unable to bind a WebSphere MQ        *
*                      JMS Connection Factory resource into    *
*                      the JNDI namespace, when the Queue      *
*                      Manager field name is left blank (null) *
*                      when defining the Connection Factory    *
*                      resource in WAS Administration. As a    *
*                      result, the Connection Factory can not  *
*                      be used by MDB or other JMS             *
*                      applications.  Message WSVR0017E can be *
*                      seen. If Messaging trace is enabled,    *
*                      MQJMS1006 exception code may be seen.   *
*                      However, some users may want to take    *
*                      advantage of a default Queue Manager    *
*                      defined on their MQ JMS installation    *
*                      rather than having to specify the       *
*                      Queue Manager name using                *
*                      WAS Administration.                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
WebSphere Application Server for z/OS throws an exception
like the following when binding a WebSphere MQ JMS Connection
Factory  defined with a blank (null) Queue Manager name.

Trace: 2005/01/04 14:12:03.738 01 t=8FB620 c=UNK key=P8
FunctionName: com.ibm.ws.runtime.component.ResourceMgrImpl
SourceId: com.ibm.ws.runtime.component.ResourceMgrImpl
Category: ERROR
ExtendedMessage: WSVR0017E: Error encountered binding the J2EE
  resource, qcf1, as jms/skqcf1 from file:///WebSphere/V5R0M0/
  AppServer/config/cells/SY1/nodes/SY1/resources.xml
com.ibm.ws.runtime.component.binder.ResourceBindingException:
invalid configuration passed to resource binding logic. REASON:
  Failed to create connection factory
at com.ibm.ejs.jms.JMSConnectionFactoryReferenceable.<init>
at com.ibm.ejs.jms.JMSResourceRefBuilderImpl.
  createNonGenericConnectionFactoryReferenceable
at com.ibm.ejs.jms.JMSResourceRefBuilderImpl.
  createNonGenericQueueConnectionFactoryReferenceable
at com.ibm.ejs.jms.JMSResourceRefBuilderImpl.
  createMQQueueConnectionFactoryReferenceable
at com.ibm.ws.runtime.component.binder.
  MQQueueConnectionFactoryBinder.getBindingObject
at com.ibm.ws.runtime.component.ResourceMgrImpl.bind
at com.ibm.ws.runtime.component.ResourceMgrImpl.
  installResourceProvider
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResource
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResources
at com.ibm.ws.runtime.component.ResourceMgrImpl.loadResources
at com.ibm.ws.runtime.component.ResourceMgrImpl.start
at com.ibm.ws.runtime.component.ContainerImpl.startComponents
at com.ibm.ws.runtime.component.ContainerImpl.start
at com.ibm.ws.runtime.component.ApplicationServerImpl.start
at com.ibm.ws.runtime.component.ContainerImpl.startComponents
at com.ibm.ws.runtime.component.ContainerImpl.start
at com.ibm.ws.runtime.component.ServerImpl.start
at com.ibm.ws.runtime.WsServer.start
at com.ibm.ws.runtime.WsServer.main
at com.ibm.ws390.orb.CommonBridge.WsServerStartup
at com.ibm.ws390.orb.ServerRegionBridge.initCSI
at com.ibm.ws390.orb.ORBEJSBridge.initCSI

In addition, one of several exceptions will be encountered when
either an MDB Listener or a user's JMS application tries to
perform JNDI lookup on this Connection Factory, since it was
not successfully bound in the namespace.  The MDB or JMS
application will then most likely fail.
Problem conclusion
WebSphere Application Server for z/OS will no longer throw
an exception when binding a WebSphere MQ JMS Connection Factory
defined using WAS Administration into the namespace when the
Queue Manager has been left blank (null). This will allow
customers with a default Queue Manager set upon their MQ JMS
installation to use this default without having to specify this
using WAS Administration.

APAR PQ98520 is associated with SERVICE LEVEL W502022 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ98520
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-12-15
Closed date 2005-01-21
Last modified date 2005-02-01

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ97067    UP05/01/26 P F501

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ98520.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ98520
IBM Group: Software Group
Modified date: Feb 1, 2005