IBM Support

IT34874: MESSAGE FLOW WITH RESEQUENCE NODE DOES NOT RELEASE IDLE ODBC CONNECTIONS

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

  • For a message flow containing a Resequence node, a transaction
    break occurs at the Resequence node. Messages are propagated
    out of the Resequence node under a new transaction and a
    separate thread to messages arriving at the node. The message
    flow processing threads handling the resequenced messages may
    connect to ODBC database resources but these connections are
    not released when they become idle. This can lead to stale
    connections being closed by a firewall such that when the
    message flow thread next tries to use them, errors are
    reported. For example, with Oracle ODBC connections the
    following errors may be seen:
    
    BIP2322E: Database error: SQL
    State '08S01'; Native Error Code '0'; Error Text '[IBM][ODBC
    Oracle Wire Protocol driver]Socket closed.'.
    BIP2322E: Database
    error: SQL State '08S01'; Native Error Code '-4'; Error Text
    '[IBM][ODBC Oracle Wire Protocol driver][Oracle]Connection
    Dead.'.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V10 and IBM App Connect
    Enterprise V11 using the Resequence node.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    For a message flow containing a Resequence node, a transaction
    break occurs at the Resequence node. Messages are propagated
    out of the Resequence node under a new transaction and using a
    separate thread to the messages arriving into the node. The
    message
    flow processing threads handling the resequenced messages may
    connect to ODBC database resources but these connections are
    not released when they become idle. This can lead to stale
    connections being closed by a firewall such that when the
    message flow thread next tries to use them, errors are reported.
    For example, with Oracle ODBC connections the following errors
    may be seen:
    
    BIP2322E: Database error: SQL State '08S01'; Native Error Code
    '0'; Error Text '[IBM][ODBC Oracle Wire Protocol driver]Socket
    closed.'.
    BIP2322E: Database error: SQL State '08S01'; Native Error Code
    '-4'; Error Text '[IBM][ODBC Oracle Wire Protocol
    driver][Oracle]Connection
    Dead.'.
    

Problem conclusion

  • The Resequence node now returns the correct return code back to
    the message flow infrastructure when it is idle so that ODBC
    connections may be released.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.23
    v11.0      11.0.0.11
    
    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

    IT34874

  • 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

    2020-11-11

  • Closed date

    2020-12-15

  • Last modified date

    2020-12-15

  • 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":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0"}]

Document Information

Modified date:
16 December 2020