IBM Support

IC86289: WMQ Z/OS RESOURCE ADAPTER: JMS ERRORS WSVR0017E AND CWWMQ0032E SEEN AFTER IMPORTING THE WMQ-RA FROM Z/OS INTO ZWAS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The WebSphere MQ Resource Adapter from an WebSphere MQ Z/OS
    installation was imported into the WebSphere Application Server
    V8.0.0.1 on z/OS.
    
    After restarting the application server, the WebSphere
    Application Server Job-log contained the following error
    messages:
    
    Trace: 2012/08/29 13:10:02.082 02 t=7E3AE8 c=UNK
    SourceId: com.ibm.ws.runtime.component.ResourceMgrImpl
    ExtendedMessage:
    BBOO0220E: WSVR0017E: Error encountered binding the J2EE
    resource, xxx,
    as xxx from
    /xxx/config/AppServer/profiles/default/config/cells/servername
    /resources.xml
    com.ibm.ws.runtime.component.binder.ResourceBindingException:
    invalid configuration passed to resource binding logic.
    REASON: Failed to create connection factory:
    
    CWWMQ0032E: An internal error has occurred. : null
    at com.ibm.ejs.jms.JMSConnectionFactoryReferenceable.<init>
    (JMSConnectionFactoryReferenceable.java:209)
    
    at com.ibm.ejs.jms.JMSResourceRefBuilderImpl.createNonGenericCon
    nectionFactoryReferenceable(JMSResourceRefBuilderImpl.java:677)
    
    at com.ibm.ejs.jms.JMSResourceRefBuilderImpl.createNonGenericCon
    nectionFactoryReferenceable(JMSResourceRefBuilderImpl.java:642)
    
    at com.ibm.ejs.jms.JMSResourceRefBuilderImpl.createMQConnectionF
    actoryReferenceable(JMSResourceRefBuilderImpl.java:564)
    
    
    
    Trace of the event shows the following NullPointerException has
    been thrown:
    
    Caused by: java.lang.NullPointerException
    
    at com.ibm.msg.client.wmq.factories.WMQComponent.getImplementati
    onInfo(WMQComponent.java:194)
    
    at com.ibm.msg.client.commonservices.trace.Trace.getVersion(Trac
    e.java:1832)
    
    at com.ibm.msg.client.commonservices.trace.Trace.setOn(Trace.jav
    a:476)
    
    at com.ibm.msg.client.services.Trace.setStatus(Trace.java:58)
    
    
    The MQXAConnectionFactory failed its initialization and was
    unavailable to be used within the application server.
    

Local fix

  • Removed JVM property settings MQJMS_TRACE_LEVEL and
    MQJMS_TRACE_DIR
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the WebSphere MQ Resource Adapter
    7.0 and 7.1 obtained from a WebSphere MQ for zOS installation,
    that is then manually installed into an Application Server, for
    example by importing into the WebSphere Application Server.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java +Java zOS
    ****************************************************************
    PROBLEM SUMMARY:
    If the WebSphere MQ Resource Adapter is being used within an
    application server environment and the Resource Adapter was
    obtained from a WebSphere MQ for zOS installation, then a
    failure occurred when attempting to use WebSphere MQ resources
    created from the Resource Adapter.
    
    The failure occurred when WebSphere MQ trace has been turned on
    using the JVM properties:
    
    MQJMS_TRACE_LEVEL
    MQJMS_TRACE_DIR
    
    
    If the Resource Adapter was installed into the WebSphere
    Application Server, then the following exceptions were seen in
    the application server logs at startup:
    
    
    Trace: 2012/08/29 13:10:02.082 02 t=7E3AE8 c=UNK
    SourceId: com.ibm.ws.runtime.component.ResourceMgrImpl
    ExtendedMessage:
    BBOO0220E: WSVR0017E: Error encountered binding the J2EE
    resource, xxx, as xxx from /xxx/config/AppServer/profiles/defau
    lt/config/cells/servername/resources.xml
    com.ibm.ws.runtime.component.binder.ResourceBindingException:
    invalid configuration passed to resource binding logic.
    REASON: Failed to create connection factory:
    CWWMQ0032E: An internal error has occurred. : null
    at com.ibm.ejs.jms.JMSConnectionFactoryReferenceable.<init>
    (JMSConnectionFactoryReferenceable.java:209)
    at com.ibm.ejs.jms.JMSResourceRefBuilderImpl.createNonGenericCon
    nectionFactoryReferenceable(JMSResourceRefBuilderImpl.java:677)
    

Problem conclusion

  • This issue was caused due to a version.properties file being
    encoded in EBCDIC rather an ASCII in the WebSphere MQ Resource
    Adapter contained within a WebSphere MQ for z/OS installation.
    
    The WebSphere MQ Resource Adapter expected to find this data
    encoded using an ASCII compliant character set, even when
    running on an EBCDIC platform such as z/OS.
    
    This APAR solves the problem by changing the WebSphere MQ
    Resource Adapter build process such that these property files
    are encoded in ASCII.
    
    Note that this problem does not affect users of the WebSphere
    Application Server v7.0, v8.0 and v8.5, with the embedded
    version of the WebSphere MQ Resource Adapter, which already has
    properties files which are encoded in the expected ASCII format.
    The problem only occurs in the WebSphere Application Server
    when the Resource Adapter is manually updated with a Resource
    Adapter obtained from the WebSphere MQ for z/OS installation.
    
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.10
    --------           --------------------
    Windows            U200352
    AIX                U853055
    HP-UX (PA-RISC)    U853082
    HP-UX (Itanium)    U853087
    Solaris (SPARC)    U853083
    Solaris (x86-64)   U853089
    iSeries            7.0.1.10
    Linux (x86)        U853084
    Linux (x86-64)     U853088
    Linux (zSeries)    U853085
    Linux (Power)      U853086
    zOS                7.0.1.10
    
                       v7.1
    Platform           Fix Pack 7.1.0.3
    --------           --------------------
    Windows            7.1.0.3
    AIX                7.1.0.3
    HP-UX (Itanium)    7.1.0.3
    Solaris (SPARC)    7.1.0.3
    Solaris (x86-64)   7.1.0.3
    iSeries            7.1.0.3
    Linux (x86)        7.1.0.3
    Linux (x86-64)     7.1.0.3
    Linux (zSeries)    7.1.0.3
    Linux (Power)      7.1.0.3
    zOS                7.1.0.3
    
    Platform           v7.5
    --------           --------------------
    Multiplatforms     7.5.0.1
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC86289

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-09-03

  • Closed date

    2012-09-25

  • Last modified date

    2012-09-25

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

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

    PM90843

Fix information

  • Fixed component name

    WMQ WINDOWS V7

  • Fixed component ID

    5724H7220

Applicable component levels

  • R701 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
31 March 2023