IBM Support

PM75183: PURGEPOOLCONTENTS MAY TAKE DOWN THE DATABASE

Fixes are available

8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
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.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.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

  • When using the mbean purgePoolContents to purge the connection
    pool, it destroys all of the connections in the pool as
    designed, but destroying all the connections and then having the
    connection pool return to a steady state can cause the database
    to crash.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using JCA mbean                      *
    *                  purgePoolContents.                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Purging all connections in a            *
    *                      connection pool can cause extra         *
    *                      stress on an already overload           *
    *                      database resulting in a crash.          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    numConnectionsToRemain was added to the mbean
    purgePoolContents to allow customers to reduce the connection
    pool down to a safe level without destorying all connections.
    Example using purgePoolContents and numConnectionsToRemain,
    start wsadmin
    set name [list Default Datasource]
    set objectName [$AdminControl queryNames *:name=$name,*]
    $AdminControl invoke $objectName showPoolContents   (You
    should have more then one connection in the pool, assuming
    multiple applications running)
    set objNameString [$AdminControl completeObjectName
    WebSphere:name=$name,*]
    set objName [java::new javax.management.ObjectName
    $objNameString]
    set parms [java::new {java.lang.Integer[]} 1 1]  (purge down
    to 1 connection)
    set signature [java::new {java.lang.String[]} 1
    java.lang.Integer]
    $AdminControl invoke_jmx $objName purgePoolContents $parms
    $signature
    $AdminControl invoke $objectName showPoolContents   (You
    should have one connection in the pool assuming for this
    example that your applications are not running.  If your
    applications are still running, the connection pool would be
    purged down to one connection and then increase in size back up
    to
    maximum connection if needed)
    

Problem conclusion

  • numConnectionsToRemain for purgePoolContents allows
    a for better control for purging connection.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.29, 8.0.0.6 and 8.5.0.2.  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

    PM75183

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-17

  • Closed date

    2013-01-07

  • Last modified date

    2013-01-07

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM75183

Modified date: 07 January 2013