IBM Support

PI81076: ServerSession numberOfNonPooledConnectionsUsed can become invalid when Exception is thrown connecting

Fixes are available

9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using non-pooled Connections, such as when using
    Eclipselink's Auditing capability to override the DataSource
    when creating a new EntityManager, a counter of non-pooled
    connections is maintained.  Unless configured to allow for
    unlimited non-pooled Connections, when a maximum is reached
    a service thread attempting to create a new non-pooled
    Connection must block until another thread releases a
    non-pooled Connection.
    
    Bugs affecting the accuracy of the non-pooled connections
    counter were found in the logic controlling the creation of
    new non-pooled connections as well as the disposal of
    non-pooled connections.  The result was an introduction of
    an inaccuracy to the counter that caused it to have a higher
    value than the actual number of non-pooled connections.
    When the number of non-pooled connections is constrained
    (the default is 50), this can lead to the counter reaching
    the maximum, preventing any new non-pooled connections from
    being created and permanently blocking threads requesting
    for new non-pooled connections.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty - Java Persistence API       *
    *                  (JPA)                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Eclipselink's counter of non-pooled     *
    *                      connections can become innaccurate and  *
    *                      lead to deadlocks                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using non-pooled Connections, such as when using
    Eclipselink's Auditing capability to override the DataSource
    when creating a new EntityManager, a counter of non-pooled
    connections is maintained.  Unless configured to allow for
    unlimited non-pooled Connections, when a maximum is reached a
    service thread attempting to create a new non-pooled Connection
    must block until another thread releases a non-pooled
    Connection.
    Bugs affecting the accuracy of the non-pooled connections
    counter were found in the logic controlling the creation of new
    non-pooled connections as well as the disposal of non-pooled
    connections.  This can occur if a DatabaseException occurs
    while
    creating the Connection or trying to dispose of it.  The result
    was an introduction of an inaccuracy to the counter that caused
    it to have a higher value than the actual number of non-pooled
    connections.  When the number of non-pooled connections is
    constrained (the default is 50), this can lead to the counter
    reaching the maximum, preventing any new non-pooled connections
    from being created and permanently blocking threads requesting
    for new non-pooled connections.
    

Problem conclusion

  • The affected pathways have been updated to catch
    DatabaseException and adjust the non-pooled connection counter
    to the correct value before rethrowing the DatabaseException.
    
    The fix for this APAR is currently targeted for inclusion in
    Liberty fix pack 17.0.0.2 and WebSphere fix pack 9.0.0.5.
    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

    PI81076

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-04

  • Closed date

    2017-05-18

  • Last modified date

    2017-06-05

  • 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

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

  • R855 PSY

       UP

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

Document Information

Modified date:
17 June 2020