IBM Support

PM80930: Oracle UCP XA Datasource results in UniversalConnectionPoolException:All connections

Fixes are available

8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The cause of the issue is that during connection close and
    subsequent cleanup, the pooledConnection object in the
    WebSphere managed connection is not being destroyed and hence
    resulting in the UCP pool getting exhausted.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Using Oracle UCP XA Datasource can      *
    *                      exhaust the Universal Connection Pool   *
    *                      (UCP)                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using the Oracle UCP XA Datasource, that is,
    oracle.ucp.jdbc.PoolXADataSourceImpl in WebSphere Application
    Server, the Universal Connection Pool can get exhausted and
    result in the following exception :
    java.sql.SQLException: Exception occurred while getting
    connection: oracle.ucp.UniversalConnectionPoolException: All
    connections in the Universal Connection Pool are in
    useDSRA0010E: SQL State = null, Error Code = 29
    at
    oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.
    java:488)
    at
    oracle.ucp.util.UCPErrorHandler.throwSQLException(UCPErrorHandle
    r.java:163)
    at
    oracle.ucp.jdbc.PoolXADataSourceImpl.getXAConnection(PoolXADataS
    ourceImpl.java:235)
    at
    oracle.ucp.jdbc.PoolXADataSourceImpl.getXAConnection(PoolXADataS
    ourceImpl.java:149)
    ..
    The problem was due to XA connection object not being
    wrapped within the managed connection and hence during
    the connection close and subsequent cleanup operation, the
    XA connection object was destroyed. This resulted in the
    Universal Connection Pool getting exhausted and resulted in
    the above exceptions.
    

Problem conclusion

  • The adapter component has been fixed to ensure that the UCP XA
    connection objects are destroyed properly upon applications
    closing the connections.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.31, 8.0.0.7 and 8.5.5.1. 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

    PM80930

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-18

  • Closed date

    2013-04-10

  • Last modified date

    2014-07-01

  • 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

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021