PM92422: CONNECTIONWAITTIMEOUTEXCEPTION ON SESSIONDB

8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
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.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

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 is sysrouted FROM one or more of the following:

  PM84596

• 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