IBM Support

PM54323: WITH ERRORDETECTIONMODEL SET TO EXCEPTIONMAPPING CONNECTION POOL DOES NOT GET PURGED IN RARE CASE

Fixes are available

7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
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.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
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.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
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

  • With errorDetectionModel set to ExceptionMapping and
    terminate the database connections ( negative test case)
    using " db2 force applications all" the JDBC Driver throws
    an XAException during start of UOW.
    
    This exception is caught by the WebSphere RRA code and
    a StaleConnectionException is instantiated. Since the SCE
    was instantiated, the existing code does not have the
    functionality to fire the connection error event and
    thereby the connection pool does not get purged.
    
    But in the case of errorDetectionModel set to
    ExceptionChecking, the above scenario results in
    the connection pool getting purged.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: With errorDetectionModel set to         *
    *                      ExceptionMapping the connection pool    *
    *                      does not get purged in rare cases       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the connection pool error detection model is configured to
    exception mapping, the stale connection exception indicates
    that the connection is no longer valid. Consider the scenario
    where the DB2 database connections are terminated using "db2
    force applications all" command and the JDBC Driver throws an
    XAException during start of UOW. This exception is caught by
    the WebSphere RRA code and a StaleConnectionException is
    instantiated and thrown back to the application.
    Typically when a StaleConnectionException results from the
    exception mapping process a connection error event is fired and
    subsequently the connection pool gets purged.  However in this
    rare case scenario the SCE is instantiated, but does
    not fire the connection error event for the pool to get purged.
    When connections are terminated at the database side,
    upon requesting a new connection, the driver throws an
    XAException. Under such condition, with
    errorDetectionModel=ExceptionMapping, you observe connection
    pool not getting purged, then with this apar you can force a
    ConnectionErrorEvent to be fired so that the connection pool
    gets purged based on the purge policy.
    Note : The APAR is not enabled by default and in order to
    enable the APAR you will have to define a datasource custom
    property on the respective datasources
    Navigate to:
    Resources > JDBC > JDBC providers > JDBC_provider > Data
    sources > (data_source) > Custom properties
    Define the following custom property :
    Property Name : fireCEEventOnSCE
    Value : true
    Restart the servers for the custom property to take effect.
    

Problem conclusion

  • The WebSphere RRA code has been changed such that the pool
    purged properly upon a StaleConnectionException when using
    ExceptionMapping as the errorDetection model.
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.23 and 8.0.0.4.  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

    PM54323

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2011-12-14

  • Closed date

    2012-03-28

  • Last modified date

    2016-02-02

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM54323

Modified date: 02 February 2016