IBM Support

IT39968: GLOBALLY COORDINATED (XA) TRANSACTIONS TO DB2 MAY REPORT AN XA PROTOCOL ERROR.

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

  • When a thread that is paricipating in globally coordinated
    transactions with IBM MQ and DB2 closes down you may see an
    error reported.
    
    The error is reported in the IBM MQ error logs because IBM MQ
    is the transcation manager used, by IBM Intergarion Bus and App
    Connect Enterprise, to coordinate global transactions with DB2.
    The error reported by IBM MQ is XAER_PROTO (-6) on xa_close()
    and it will refer to
    the DataFlowEngibe process.
    The error can occur when a thread reaches its maximum 'database
    connection idle' time and attempts to disconnect.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise V11 or V12, or IBM
    Integration Bus V10, who use globally coordinated (XA)
    transactions with a Db2 database.
    
    
    Platforms affected:
    Windows on x86-64 platform, Solaris SPARC platform, Solaris
    x86-64 platform, Linux on zSeries platform, Linux on x86-64
    platform, Linux on Power platform, HP-UX Itanium platform, AIX
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a thread that has been involved in globally coordinated
    transactions with a Db2 database is released, because it has
    become idle, there is the possibility that an XAER_PROTO (-6)
    error can be reported on the xa_close call. If this error has
    occurred it will be reported in the IBM MQ queue manager error
    logs as IBM MQ is coordinating the global transactions.
    

Problem conclusion

  • The management of the contexts used for communication with Db2
    has been changed to resolve this issue.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.26
    v11.0      11.0.0.17
    v12.0      12.0.4.0
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT39968

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-02-15

  • Closed date

    2022-03-11

  • Last modified date

    2022-03-11

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0"}]

Document Information

Modified date:
12 March 2022