IC87020: WebSphere MQ V7.1: XA TRANSACTIONS ROLLBACK WHEN PERFORMING AN MQPUT TO A QUEUE THAT IS PUT INHIBITED

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • In WebSphere MQ V7.1: An XA Transaction will roll back after
    attempting to PUT to a queue that is PUT inhibited. At WebSphere
    MQ V6 this transaction would not be rolled back
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the WebSphere MQ classes for Java,
    which are making use of XA Transactions and see an
    MQRC_PUT_INHIBITED exception returned to the client after
    attempting to PUT to a queue
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java +Java zOS
    ****************************************************************
    PROBLEM SUMMARY:
    In V7.1 of the WebSphere MQ Classes for Java, if an
    MQRC_PUT_INHIBITED exception is flowed back to the client whilst
    an XA Transaction is in progress the WebSphere MQ Classes for
    Java will close the underlying XA Connection and XA Session,
    which in turn causes xa_end to be called for said session.
    
    When the transaction has completed the Transaction Manager then
    attempts to call commit which in turn calls xa_end for a second
    time on the same XA session, this results in the following
    XAException and accompanying FFDC which results in the
    transaction rolling back:
    
    XAException in end
    javax.transaction.xa.XAException: 'xa_end' errorCode '100'
    at com.ibm.mq.jmqi.JmqiXAResource.end
    
    The JMS Specification states that the application server
    (Transaction Manager) must control the transaction management of
    the underlying XASession. The current behavior of the WebSphere
    MQ Client does not conform to this.
    

Problem conclusion

  • The WebSphere MQ Classes for Java no longer close the underlying
    XA Session when an exception is flowed back
    to the client whilst an XA Transaction is in progress. This
    change ensures that transaction management is only performed by
    the Transaction Manager as per the JMS Specification. This
    mimics the WebSphere MQ V6 behavior.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       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
    
                       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
    
    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

    IC87020

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-09

  • Closed date

    2012-12-21

  • Last modified date

    2012-12-21

  • 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

    WMQ WINDOWS V7

  • Fixed component ID

    5724H7220

Applicable component levels

  • R710 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere MQ
APAR / Maintenance

Software version:

710

Reference #:

IC87020

Modified date:

2012-12-21

Translate my page

Machine Translation

Content navigation