IBM Support

PM84596: CONNECTIONWAITTIMEOUTEXCEPTION ON SESSIONDB

Fixes are available

8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
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.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • ConnectionWaitTimeoutException on SessionDB
    
    When a web request arrives, the web container gets a session
    database connection, and then gets a DatabaseSession lock.
    
    Here is the example of thread stack.
    -------------------------------------
    at
    com/ibm/ws/session/store/db/DatabaseHashMap.overQualLastAccessTi
    meUpdate
    (DatabaseHashMap.java:1699)
    at
    com/ibm/ws/session/store/common/BackedHashMap.getSession(BackedH
    ashMap.j
    ava:184)
    at
    com/ibm/ws/session/store/common/BackedHashMap.getSession(BackedH
    ashMap.j
    ava:109)
    at
    com/ibm/ws/session/store/common/BackedStore.getSession(BackedSto
    re.java:
    71)
    at
    com/ibm/ws/session/store/memory/MemoryStore.getSession(MemorySto
    re.java:
    690)
    at
    com/ibm/ws/session/SessionManager.getSessionFromStore(SessionMan
    ager.jav
    a:490)
    at
    com/ibm/ws/session/SessionManager.getSession(SessionManager.java
    :474)
    at
    com/ibm/ws/session/SessionManager.getSession(SessionManager.java
    :460)
    at
    com/ibm/ws/session/SessionManager.getSession(SessionManager.java
    :674)
    at
    com/ibm/ws/session/SessionContext.getIHttpSession(SessionContext
    .java:44
    1)
    at
    com/ibm/ws/session/SessionContext.sessionPreInvoke(SessionContex
    t.java:5
    59)
    -------------------------------------
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server Version 7, *
    *                  8, and 8.5 users of database session        *
    *                  persistence.                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: The Session Manager may not be able to  *
    *                      process session database updates due to *
    *                      connection errors.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the session database connection pool is exhausted due to a
    large number of concurrent requests, a
    ConnectionWaitTimeoutException may occur.
    

Problem conclusion

  • Code changes were made to the Session Manager to synchronize
    the session locks and the database 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

    PM84596

  • 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

    2013-03-12

  • Closed date

    2013-05-23

  • Last modified date

    2013-05-23

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PM92422

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 #: PM84596

Modified date: 23 May 2013