IBM Support

IT38043: MESSAGE FLOW STOPS PROCESSING WHEN AN ODBC CONNECT TO DB2 FAILS.

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

  • The Db2 client driver is waiting indefinately for a response to
    connect request to the Db2 server
    This stops the flow from processing its messages.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise v11 and v12 using ODBC
    connections to a secure database server.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The Db2 ODBC driver may hang under certain circumstances when
    using a TLS connection leaving the thread unable to process
    messages. A stack dump will show a thread hung in the
    SQLConnect() function. An example stack trace would include
    
    __recv
    ??
    ??
    ??
    ??
    ??
    ??
    ??
    ??
    ??
    gsk_secure_soc_init
    sqlccSSLSocketSetup
    sqlcctcpconnr
    sqlccconnr
    sqljcCommConnect
    sqljcCmnMgrInit
    sqljrCreateTransport
    sqljrAssociateTransport
    sqljrConnectBasedOnCatalog
    sqljrInternalConnect
    sqljrFindBestAddressAndConnect
    sqljrDrdaArAuthenticate
    sqlexAppAuthenticate
    sqljrDrdaArConnect
    sqleUCdrdaARinit
    sqleUCappConnect
    CLI_sqlConnect
    SQLConnect2
    

Problem conclusion

  • The environment variable MQSI_ODBC_SQLCONNECT_TIMEOUT has been
    introduced. If this environment variable is set then its value
    will be interpreted as the number of seconds that a SQLConnect()
    call is allowed to take. If this timeout is exceeded then the
    integration server is restarted. A BIP2111 fatal exception will
    be logged stating "database timeout". If the integration server
    does not shut down cleanly within 120 seconds then an abend will
    be triggered to force the restart.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v11.0      11.0.0.15
    v12.0      12.0.2.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

    IT38043

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-08-17

  • Closed date

    2021-10-08

  • Last modified date

    2021-10-08

  • 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

    APP CONNECT ENT

  • Fixed component ID

    5724J0550

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00"}]

Document Information

Modified date:
13 October 2021