IBM Support

IT30199: MQ resource adapter in Liberty for z/OS throws exception with "The method xa_open has failed with errorCode -5"

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • After migrating from using the IBM MQ V9.1.2.0 resource adapter
    in WebSphere Liberty z/OS Connect to the IBM MQ V9.1.3.0
    resource adapter, an exception is thrown during an XA Open call
    when connected to a z/OS queue sharing group, preventing a:
    
      javax.resource.spi.ManagedConnection
    
    from being created.  The exception thrown and subsequently
    reported in the WebSphere Liberty z/OS Connect job log, is as
    follows:
    
    J2CA0078E: An exception was caught while trying to obtain a
    javax.transaction.xa.XAResource from a ManagedConnection on
    DataSource
    jms/mqConnectionFactory.
    The exception is:
    com.ibm.mq.connector.DetailedResourceException: MQJCA1013:
    Failed
      at
    com.ibm.mq.connector.services.JCAExceptionBuilder.buildException
      at
    com.ibm.mq.connector.services.JCAExceptionBuilder.buildException
      at
    com.ibm.mq.connector.outbound.ManagedConnectionImpl.getXAResourc
    e
      at com.ibm.ejs.j2c.XATransactionWrapper.initialize
      at "internal classes"
      at
    com.ibm.mq.connector.outbound.ConnectionFactoryImpl.createManage
    dJMSConnection
      at
    com.ibm.mq.connector.outbound.ConnectionFactoryImpl.createConnec
    tionInternal
      at
    com.ibm.mq.connector.outbound.ConnectionFactoryImpl.createConnec
    tion
      at
    com.ibm.mq.connector.outbound.ConnectionFactoryImpl.createConnec
    tion
      at com.ibm.mq.zosconnect.MQServiceInvocation.createConnection
     Caused by: com.ibm.msg.client.jms.DetailedJMSException:
    JMSWMQ1068: Failed to obtain the XA resource.
     IBM MQ classes for JMS failed to create an XA resource due to
    an error.
     See the linked XAException for more information.
      at sun.reflect.NativeConstructorAccessorImpl.newInstance0
      at sun.reflect.NativeConstructorAccessorImpl.newInstance
      at sun.reflect.DelegatingConstructorAccessorImpl.newInstance
      at java.lang.reflect.Constructor.newInstance
      at
    com.ibm.msg.client.commonservices.j2se.NLSServices.createExcepti
    on
      at
    com.ibm.msg.client.commonservices.nls.NLSServices.createExceptio
    n
      at com.ibm.msg.client.wmq.internal.WMQXASession.<init>
      at
    com.ibm.msg.client.wmq.internal.WMQXAConnection.createXASession
      at
    com.ibm.msg.client.jms.internal.JmsXAConnectionImpl.createXASess
    ion
      at com.ibm.mq.jms.MQXAConnection.createXASession
      at
    com.ibm.mq.connector.outbound.ManagedConnectionImpl.getXAResourc
    e
      ... 12 more
     Caused by: javax.transaction.xa.XAException: The method
    'xa_open' has failed with errorCode '-5'.
       at com.ibm.mq.jmqi.JmqiXAResource.<init>
       at com.ibm.mq.jmqi.JmqiXAResource.getInstance
       at com.ibm.mq.jmqi.JmqiEnvironment.newJmqiXAResource
       at com.ibm.msg.client.wmq.internal.WMQXASession.<init>
    
    J2CA0045E: Connection not available while invoking method
    createOrWaitForConnection for resource jms/mqConnectionFactory.
    

Local fix

  • Use the BINDINGS transport mode, if possible.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects MQ classes for JMS applications that use the
    IBM MQ V9.1.3.0 classes for JMS to connect to z/OS queue sharing
    groups using the CLIENT transport mode and perform work under XA
    transactions.
    
    
    Platforms affected:
    z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    In MQ V9.1.3.0, a code change made it possible for a z/OS queue
    sharing group name to be used within an "xa_open" string in the
    MQ classes for JMS:
    
    https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.1.0/com.
    ibm.mq.con.doc/q016550_.htm
    
    However, this was not expected later in the code and XA Open
    calls were failed with the XA reason XAER_INVAL (-5).
    

Problem conclusion

  • The MQ classes for JMS have been updated to ensure z/OS queue
    sharing group names are handled correctly in xa_open strings.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 CD    9.1.4
    
    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

    IT30199

  • Reported component name

    MQ APPLIANCE M2

  • Reported component ID

    5737H4700

  • Reported release

    913

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-09-05

  • Closed date

    2019-09-17

  • Last modified date

    2019-09-17

  • 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

    MQ APPLIANCE M2

  • Fixed component ID

    5737H4700

Applicable component levels

  • R913 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"913","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 September 2019