Deadlock at com.ibm.servlet.personalization.sessiontracking .SessionData.setLastAccessedTime
 Product documentation
 
Abstract
There is a restriction that applications cannot synchronize on session objects as it may result in a deadlock.
 
 
Content
Applications cannot synchronize session objects inside of their servlets or JavaServer Pages (JSP) because a deadlock with the session manager may occur. The deadlock occurs because the session manager does not expect the use of more than one locking mechanism. You can ensure that only one request can access the session at a time through the use of the configuration option, "allow serial access".
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Sessions and Session Management
Operating system(s): HP-UX
Software version: 4.0
Software edition:
Reference #: 7007028
IBM Group: Software Group
Modified date: Dec 12, 2005