APAR status
Closed as program error.
Error description
While running the session trace the Application Server
experienced a deadlock condition. Eventually all request will
become hung and the Application Server clone will be
unresponsive.
If a threaddump is taken on Solaris it will contain somehting
similar to the following:
FOUND A JAVA LEVEL DEADLOCK:
----------------------------
"Servlet.Engine.Transports : 299291":
waiting to lock monitor 0x1eeea0 (object 0x579f7d28, a com.ibm.
ws.webcontainer.httpsession.DatabaseSessionData),
which is locked by "Servlet.Engine.Transports : 299227"
"Servlet.Engine.Transports : 299227":
waiting to lock monitor 0x1ee7a0 (object 0x3a58bf50, a com.ibm.
ws.webcontainer.httpsession.BackedHashtable),
which is locked by "Servlet.Engine.Transports : 299291"
The threads involved were similar to the following:
Java Stack for "Servlet.Engine.Transports : 299291":
==========
at com.ibm.ws.webcontainer.httpsession.DatabaseSessionData.
toString(DatabaseSessionData.java:699)
- waiting to lock <0x579f7d28> (a com.ibm.ws.webcontainer.
httpsession.DatabaseSessionData)
at java.lang.String.valueOf(Unknown Source)
at java.lang.StringBuffer.append(Unknown Source)
- locked <0x57aeaa88> (a java.lang.StringBuffer)
at com.ibm.ws.webcontainer.httpsession.SessionSimpleLRUHashMap.
get(SessionSimpleLRUHashMap.java:200)
at com.ibm.ws.webcontainer.httpsession.BackedHashtable.
superGet(BackedHashtable.java:2656)
at com.ibm.ws.webcontainer.httpsession.BackedHashtable.
remove(BackedHashtable.java:465)
- locked <0x3a58bf50> (a com.ibm.ws.webcontainer.httpsession.
BackedHashtable)
at
com.ibm.ws.webcontainer.httpsession.SessionContext.tableRemove
(SessionContext.java:1962)
at com.ibm.ws.webcontainer.httpsession.SessionContext.
removeSessionFromTable(SessionContext.java:898)
at com.ibm.ws.webcontainer.httpsession.DatabaseSessionContext.
removeSessionFromTable(DatabaseSessionContext.java:391)
at com.ibm.ws.webcontainer.httpsession.SessionContext.
notifySessionInvalidated(SessionContext.java:886)
at com.ibm.ws.webcontainer.httpsession.SessionData.invalidate
(SessionData.java:594)
- locked <0x571e5b60> (a com.ibm.ws.webcontainer.httpsession.
DatabaseSessionData)
at myapplication.invalidate(myapplication.java...)
...
=========
Java Stack for "Servlet.Engine.Transports : 299227":
==========
at com.ibm.ws.webcontainer.httpsession.SessionSimpleLRUHashMap.
remove(SessionSimpleLRUHashMap.java:207)
- waiting to lock <0x3a58bf50> (a com.ibm.ws.webcontainer.
httpsession.BackedHashtable)
at com.ibm.ws.webcontainer.httpsession.BackedHashtable.
superRemove(BackedHashtable.java:2640)
at com.ibm.ws.webcontainer.httpsession.BackedHashtable.
retrieveSession(BackedHashtable.java:1616)
- locked <0x579f7d28> (a com.ibm.ws.webcontainer.httpsession.
DatabaseSessionData)
at com.ibm.ws.webcontainer.httpsession.BackedHashtable.
getSession(BackedHashtable.java:1521)
at com.ibm.ws.webcontainer.httpsession.BackedHashtable.get
(BackedHashtable.java:1909)
at com.ibm.ws.webcontainer.httpsession.SessionContext.tableGet
(SessionContext.java:1951)
at com.ibm.ws.webcontainer.httpsession.SessionContext.
findSession(SessionContext.java:1196)
a t com.ibm.ws.webcontainer.httpsession.SessionContext.
getIHttpSession(SessionContext.java:1233)
at com.ibm.ws.webcontainer.httpsession.SessionContext.
getIHttpSession(SessionContext.java:2184)
at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.
getSession(WebAppDispatcherContext.java:178)
at com.ibm.ws.webcontainer.srt.SRTServletRequestContext.
getSession(SRTServletRequestContext.java:211)
...
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users who *
* turn on the trace of the Session component. *
****************************************************************
* PROBLEM DESCRIPTION: When session trace is turned on, it *
* might cause deadlock, thus the system *
* might hang. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A java deadlock might happen if session trace is turned on
Problem conclusion
Rephase the trace so that deadlock will not occur
Temporary fix Comments
APAR information |
APAR number |
PQ83345 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00H |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-01-16 |
Closed date |
2004-06-11 |
Last modified date |
2004-06-11 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|