IBM Support

IT36752: MQ generates unnecessary Informational FDC reporting AT040010 atxClose arcE_XAER_PROTO

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

  • A queue manager will write an information FDC with the following
    details:
    
    AT040010
    atxClose
    arcE_XAER_PROTO
    
    when an external transaction manager calls xa_close on a thread
    that has open or suspended associations with transactions.
    
    This xa_close call from the transaction manager is strictly
    outside of the protocol defined by the XA Specification, but it
    does not need to be notified to the MQ administrator, via an FDC
    or any other means.
    

Local fix

  • The FDCs do not represent a concern within MQ code, and can be
    ignored.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Administrators of queue managers where connections are made from
    Application Servers, and in which XA transactions are being
    used.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    On the rare occasions where the Application Server crashes or is
    ended abruptly by the administrator, or by the system rebooting,
    the Application Server Transaction Manager component can call
    xa_close on its connection to the queue manager, without first
    Ending its Association with an open transaction.
    
    The queue manager deals correctly with the call by returning the
    correct return code.  It also deals correctly with the ending of
    the connection, by rolling back unprepared transactions.
    However, the queue manager also writes an FDC complaining about
    the out-of-protocol xa_close call it has received.  This FDC can
    cause concern to an MQ administrator because it is not clear
    that it is OK to ignore.
    

Problem conclusion

  • This APAR removes the FDC, as it does not represent any
    significant concern within the MQ code.
    
    If you wish to continue receiving this FDC in these
    circumstances, then set AMQ_ATXCLOSE_PROBE10=1 in the
    environment before starting the queue manager.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.9
    v9.2 LTS   9.2.0.3
    v9.x CD    9.2.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

    IT36752

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-04-30

  • Closed date

    2021-06-30

  • Last modified date

    2021-06-30

  • 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

    IBM MQ BASE MP

  • Fixed component ID

    5724H7271

Applicable component levels

[{"Type":"MASTER","Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Version":"All Versions"}]

Document Information

Modified date:
01 July 2021