IBM Support

IC97579: WEBSPHERE MQ V7.0.1.10 JMS CLIENT JBOSSAPPLICATION FAILS WITH MESSAGE ARJUNA016027 ON RED HAT LINUX

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Enduser has a JMS client application running on Red Hat
    Enterprise Application Platform (EAP) 6.1.1 and WMQ v7.0.1.10.
    The application fails with a XA exception error written in the
    JBoss logs:
    
    WARN ■com.arjuna.ats.jta (Periodic Recovery)
    ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception
    XAException.XAER_INVAL: javax.transaction.xa.XAException:
    The method 'xa_recover' has failed with errorCode '-5'.
    .
    The application server does not crash, however the application
    has to be
    stopped and restarted.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects:
    
    - Users of JBoss 6.1.1 using the WebSphere MQ Resource Adapter
    in a scenario which causes the transaction manager to call
    xa_recover on the resource adapter.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    The transaction manager within the JBOSS application makes two
    calls to the WebSphere MQ Resource Adapter as part of XA
    recovery. One call to start recovery and one call to end
    recovery. The WebSphere MQ Resource Adapter incorrectly
    interpreted the call to end recovery, and created a new recovery
    object. This new recovery object could not take any further
    action, as the transaction manager had passed a flag
    indicating that recovery processing should be ended, resulting
    in the XAER_INVAL (-5) error code being returned to the
    transaction manager.
    

Problem conclusion

  • The WebSphere MQ Resource Adapter has been updated such that a
    new recovery object is not created when a call to end recovery
    is made by the transaction manager. Instead, the call to end
    recovery is passed to the existing recovery object as expected.
    
    | MDVREGR 7.0.1-WS-MQ-AixPPC64-FP0010 |
    | MDVREGR 7.0.1-WS-MQ-HpuxIA64-FP0010 |
    | MDVREGR 7.0.1-WS-MQ-HpuxPaRISC64-FP0010 |
    | MDVREGR 7.0.1-WS-MQ-LinuxIA32-FP0010 |
    | MDVREGR 7.0.1-WS-MQ-LinuxPPC64-FP0010 |
    | MDVREGR 7.0.1-WS-MQ-LinuxS390X-FP0010 |
    | MDVREGR 7.0.1-WS-MQ-LinuxX64-FP0010 |
    | MDVREGR 7.0.1-WS-MQ-SolarisSparc64-FP0010 |
    | MDVREGR 7.0.1-WS-MQ-SolarisX64-FP0010 |
    | MDVREGR 7.0.1-WS-MQ-Windows-FP0010 |
    
    | MDVREGR 7.0.1-WS-MQ-AixPPC64-FP0011 |
    | MDVREGR 7.0.1-WS-MQ-HpuxIA64-FP0011 |
    | MDVREGR 7.0.1-WS-MQ-HpuxPaRISC64-FP0011 |
    | MDVREGR 7.0.1-WS-MQ-LinuxIA32-FP0011 |
    | MDVREGR 7.0.1-WS-MQ-LinuxPPC64-FP0011 |
    | MDVREGR 7.0.1-WS-MQ-LinuxS390X-FP0011 |
    | MDVREGR 7.0.1-WS-MQ-LinuxX64-FP0011 |
    | MDVREGR 7.0.1-WS-MQ-SolarisSparc64-FP0011 |
    | MDVREGR 7.0.1-WS-MQ-SolarisX64-FP0011 |
    | MDVREGR 7.0.1-WS-MQ-Windows-FP0011 |
    
    
    | MDVREGR 7.1.0-WS-MQ-AixPPC64-FP0003 |
    | MDVREGR 7.1.0-WS-MQ-HpuxIA64-FP0003 |
    | MDVREGR 7.1.0-WS-MQ-HpuxPaRISC64-FP0003 |
    | MDVREGR 7.1.0-WS-MQ-LinuxIA32-FP0003 |
    | MDVREGR 7.1.0-WS-MQ-LinuxPPC64-FP0003 |
    | MDVREGR 7.1.0-WS-MQ-LinuxS390X-FP0003 |
    | MDVREGR 7.1.0-WS-MQ-LinuxX64-FP0003 |
    | MDVREGR 7.1.0-WS-MQ-SolarisSparc64-FP0003 |
    | MDVREGR 7.1.0-WS-MQ-SolarisX64-FP0003 |
    | MDVREGR 7.1.0-WS-MQ-Windows-FP0003 |
    
    | MDVREGR 7.1.0-WS-MQ-AixPPC64-FP0004 |
    | MDVREGR 7.1.0-WS-MQ-HpuxIA64-FP0004 |
    | MDVREGR 7.1.0-WS-MQ-HpuxPaRISC64-FP0004 |
    | MDVREGR 7.1.0-WS-MQ-LinuxIA32-FP0004 |
    | MDVREGR 7.1.0-WS-MQ-LinuxPPC64-FP0004 |
    | MDVREGR 7.1.0-WS-MQ-LinuxS390X-FP0004 |
    | MDVREGR 7.1.0-WS-MQ-LinuxX64-FP0004 |
    | MDVREGR 7.1.0-WS-MQ-SolarisSparc64-FP0004 |
    | MDVREGR 7.1.0-WS-MQ-SolarisX64-FP0004 |
    | MDVREGR 7.1.0-WS-MQ-Windows-FP0004 |
    
    
    | MDVREGR 7.5.0-WS-MQ-AixPPC64-FP0001 |
    | MDVREGR 7.5.0-WS-MQ-HpuxIA64-FP0001 |
    | MDVREGR 7.5.0-WS-MQ-HpuxPaRISC64-FP0001 |
    | MDVREGR 7.5.0-WS-MQ-LinuxIA32-FP0001 |
    | MDVREGR 7.5.0-WS-MQ-LinuxPPC64-FP0001 |
    | MDVREGR 7.5.0-WS-MQ-LinuxS390X-FP0001 |
    | MDVREGR 7.5.0-WS-MQ-LinuxX64-FP0001 |
    | MDVREGR 7.5.0-WS-MQ-SolarisSparc64-FP0001 |
    | MDVREGR 7.5.0-WS-MQ-SolarisX64-FP0001 |
    | MDVREGR 7.5.0-WS-MQ-Windows-FP0001 |
    
    | MDVREGR 7.5.0-WS-MQ-AixPPC64-FP0002 |
    | MDVREGR 7.5.0-WS-MQ-HpuxIA64-FP0002 |
    | MDVREGR 7.5.0-WS-MQ-HpuxPaRISC64-FP0002 |
    | MDVREGR 7.5.0-WS-MQ-LinuxIA32-FP0002 |
    | MDVREGR 7.5.0-WS-MQ-LinuxPPC64-FP0002 |
    | MDVREGR 7.5.0-WS-MQ-LinuxS390X-FP0002 |
    | MDVREGR 7.5.0-WS-MQ-LinuxX64-FP0002 |
    | MDVREGR 7.5.0-WS-MQ-SolarisSparc64-FP0002 |
    | MDVREGR 7.5.0-WS-MQ-SolarisX64-FP0002 |
    | MDVREGR 7.5.0-WS-MQ-Windows-FP0002 |
    
    | MDVREGR 7.5.0-WS-MQ-AixPPC64-FP0003 |
    | MDVREGR 7.5.0-WS-MQ-HpuxIA64-FP0003 |
    | MDVREGR 7.5.0-WS-MQ-HpuxPaRISC64-FP0003 |
    | MDVREGR 7.5.0-WS-MQ-LinuxIA32-FP0003 |
    | MDVREGR 7.5.0-WS-MQ-LinuxPPC64-FP0003 |
    | MDVREGR 7.5.0-WS-MQ-LinuxS390X-FP0003 |
    | MDVREGR 7.5.0-WS-MQ-LinuxX64-FP0003 |
    | MDVREGR 7.5.0-WS-MQ-SolarisSparc64-FP0003 |
    | MDVREGR 7.5.0-WS-MQ-SolarisX64-FP0003 |
    | MDVREGR 7.5.0-WS-MQ-Windows-FP0003 |
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.1.12
    v7.1       7.1.0.5
    v7.5       7.5.0.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

    IC97579

  • 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

    2013-11-11

  • Closed date

    2014-01-21

  • Last modified date

    2014-02-18

  • 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

  • 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