IBM Support

IT19916: MESSAGES CAN BECOME STUCK ON THE MQ INPUT QUEUE WHEN AN IDLE XA ODBC CONNECTION IS FORCIBLY CLOSED BY A FIREWALL.

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

  • IBM Integration Bus XA database connections are not released
    when
    they are idle. This can lead to problems when these connections
    pass through a firewall that closes inactive connections. While
    no database updates are lost it is possible to end up with
    messages stuck on the MQ Input queue.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V10.0 on Linux, Unix or Windows
    who use XA coordination when accessing a database via ODBC.
    
    
    Platforms affected:
    Windows on x86-64 platform, Windows on x86 platform, Solaris
    SPARC platform, Solaris x86-64 platform, Linux on zSeries
    platform, Linux on x86-64 platform, Linux on x86 platform, Linux
    on Power platform, HP-UX Itanium platform, AIX
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When idle XA coordinated database connections are forcibly
    closed by a firewall, subsequent messages become stuck on the
    input queue.  Manual intervention is then needed to resolve
    these transactions.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT19916

  • 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

    2017-03-28

  • Closed date

    2017-05-24

  • Last modified date

    2017-05-24

  • 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

  • RA00 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020