[
https://jira.jboss.org/jira/browse/JBAS-7844?page=com.atlassian.jira.plug...
]
Brian Stansberry moved EJBTHREE-2055 to JBAS-7844:
--------------------------------------------------
Project: JBoss Application Server (was: EJB 3.0)
Key: JBAS-7844 (was: EJBTHREE-2055)
Component/s: Clustering
Web (Tomcat) service
(was: cache)
(was: Clustering)
Security: Public
Prevent concurrent access to HttpSession on different nodes
-----------------------------------------------------------
Key: JBAS-7844
URL:
https://jira.jboss.org/jira/browse/JBAS-7844
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Clustering, Web (Tomcat) service
Reporter: Brian Stansberry
Require a node's cache to take "ownership" of an SFSB context before
returning it.
A cache that creates the SFSB context can take ownership without any cluster-wide
message.
A cache that has taken ownership can lock it during subsequent requests. Doing this does
not require any cluster-wide message.
A cache that doesn't have ownership of an SFSB context must request ownership via a
cluster-wide message. This will be granted, but not until any concurrently executing
requests on the owning node have completed.
If the node owning the session does not respond to the request to give up ownership (e.g.
it has crashed) ownership is acquired.
Code for this locking function exists in AS; needs to be extracted out into ha-server-api
(JBCLUSTER-223)
The same concept will be applied to web sessions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira