[jboss-jira] [JBoss JIRA] Resolved: (JBAS-7844) Prevent concurrent access to HttpSession on different nodes

Paul Ferraro (JIRA) jira-events at lists.jboss.org
Tue Nov 16 13:03:46 EST 2010


     [ https://jira.jboss.org/browse/JBAS-7844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ferraro resolved JBAS-7844.
--------------------------------

         Assignee: Paul Ferraro  (was: Vladimir Blagojevic)
    Fix Version/s: 6.0.0.CR1
       Resolution: Done


> Prevent concurrent access to HttpSession on different nodes
> -----------------------------------------------------------
>
>                 Key: JBAS-7844
>                 URL: https://jira.jboss.org/browse/JBAS-7844
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>            Reporter: Brian Stansberry
>            Assignee: Paul Ferraro
>             Fix For: 6.0.0.CR1
>
>
> Require a node's cache to take "ownership" of an session 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 SFSB contexts.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list