IBM Support

IT34228: JDBC DATABASE CALL TIMEOUT CANNOT BE SET MORE THAN 10 MINUTES.

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 default JDBC database call timeout of a message flow is 15
    seconds. This can be increased to a maximum of only 600 seconds
    with environment variable MQSI_POOL_DBCALL_TIMEOUT. Some JDBC
    batch processing might need a larger timeout value and this APAR
    allows to set a value larger than 600 seconds. Also the default
    JDBC database call timeout value is changed to 60 seconds from
    15 seconds.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise V11.0 and IBM
    Integration Bus V10.0 using pooled JDBC connections
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The default timeout for a JDBC database call using a pooled
    connection is 15 seconds. This can be increased to a maximum of
    only 600 seconds with the environment variable
    MQSI_POOL_DBCALL_TIMEOUT. Some JDBC batch processing might need
    a larger timeout value and this APAR allows the user to set a
    value of up to 18000 seconds. Also the default timeout for a
    JDBC database call is changed to 60 seconds from 15 seconds.
    

Problem conclusion

  • The product now allows the user to set a larger timeout value
    for JDBC operations performed by pooled connections, up to 18000
    seconds, with the environment variable MQSI_POOL_DBCALL_TIMEOUT.
    Also, the default timeout value is now 60 seconds, changed from
    15 seconds.
    
    ---------------------------------------------------------------
    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

    IT34228

  • 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-09-16

  • 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