APAR status
Closed as program error.
Error description
Reports that the Application server hangs frequently during
Peak Load. Thread dumps collected during the Hang, indicate
a Deadlock in Session Manager component, during Session
PreInvoke and PostInvoke Operations.
-- The threads invloved in the Deadlock have the following stack
----------------------------------------------------------------
Found one Java-level deadlock:
=============================
"Servlet.Engine.Transports : 125":
waiting to lock monitor 0x000e6938 (object 0xc53ed000, a
com.ibm.ws.webcontainer.httpsession.Ses
which is held by "Servlet.Engine.Transports : 195"
"Servlet.Engine.Transports : 195":
waiting to lock monitor 0x0150b380 (object 0xc53e7b88, a
java.util.LinkedList),
which is held by "Servlet.Engine.Transports : 125"
Java stack information for the threads listed above:
===================================================
"Servlet.Engine.Transports : 125":
com.ibm.ws.webcontainer.httpsession.SessionContext.sessionPreInv
oke(SessionContext.java:2649)
- waiting to lock <0xc53ed000> (a
com.ibm.ws.webcontainer.httpsession.SessionData$SessionLock)
- locked <0xc53e7b88> (a java.util.LinkedList)
- locked <0xc53ed050> (a
com.ibm.ws.webcontainer.httpsession.SessionData$SessionLock)
"Servlet.Engine.Transports : 195":
com.ibm.ws.webcontainer.httpsession.SessionContext.sessionPreInv
oke(SessionContext.java:2646)
- waiting to lock <0xc53e7b88> (a java.util.LinkedList)
- locked <0xc53ed000> (a
com.ibm.ws.webcontainer.httpsession.SessionData$SessionLock)
com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sessionPr
eInvoke(
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(
----------------------------------------------------------------
Local fix
disable "Serialize session access" in Session Manager
Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users who *
* enable the option "enable serial access to *
* session" *
****************************************************************
* PROBLEM DESCRIPTION: The following deadlock occurs: *
* "Servlet.Engine.Transports : 125": *
* waiting to lock monitor 0x000e6938 *
* (object 0xc53ed000, a com.ibm.ws. *
* webcontainer.httpsession.SessionData *
* $SessionLock), *
* which is held by "Servlet.Engine. *
* Transports : 195" *
* "Servlet.Engine.Transports : 195": *
* waiting to lock monitor 0x0150b380 *
* (object 0xc53e7b88, *
* a java.util.LinkedList), *
* *
* which is held by "Servlet.Engine. *
* Transports : 125" *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A deadlock happens when you enable "enable session serial
access" in a high load environment.
Problem conclusion
The code has been re-designed to avoid the deadlock
situation.
The fix for this APAR is currently targeted for inclusion
in 5.02.14, 5.1.1.8 and 6.0.2.5.
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 |
PK09786 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
10S |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-08-12 |
Closed date |
2005-09-30 |
Last modified date |
2005-11-29 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WAS BASE 5.0 |
Fixed component ID |
5630A3600 |
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 |
|