IBM Support

PI96004: WHEN USING A JDBC 4.0 DRIVER IN WAS V9.0, CONNECTION, A TIMED OUT TRANSACTION CANNOT PROPERLY CLOSE CONNECTIONS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a transaction is timed out and by the time the transaction
    ends, the transaction manager will try to rollback and release
    the connection, but if you are using JDBC 4.0 compliant driver,
    the rollback will happen but the connections will stay in the
    pool showing used by application. This will cause long open
    connections and might lead to connection pool exhaustion.
    

Local fix

  • Use JDBC 4.1 compliant JDBC driver
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using a JDBC 4.0 or older JDBC       *
    *                  driver                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using a JDBC 4.0 or lower          *
    *                      compliant driver, the connections are   *
    *                      not properly closed when a              *
    *                      transaction timeout occurs.             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This only affects JDBC compliance level 4.0 and older JDBC
    drivers. When using an affected driver the connections are not
    properly closed when a transaction timeout occurs. This will
    cause the connections to be held open and could lead to the
    connection pool becoming full if there a lot of transaction
    timeouts. FFDCs for the following exception will also be
    created:
    java.lang.AbstractMethodError:
    java/sql/Connection.abort(Ljava/util/concurrent/Executor;)
    

Problem conclusion

  • The code was updated so that connections are properly closed
    for JDBC compliant 4.0 and older drivers.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 9.0.0.8.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI96004

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-03-29

  • Closed date

    2018-05-18

  • Last modified date

    2018-05-18

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
18 October 2021