[jboss-jira] [JBoss JIRA] Updated: (JBAS-3720) Change structure of ClusteredSSO data in tree cache to avoid lock issues

[Brian Stansberry (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-3720?page=all ]

Brian Stansberry updated JBAS-3720:
-----------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
                       (was: JBossAS-5.0.0.CR1)

> Change structure of ClusteredSSO data in tree cache to avoid lock issues
> ------------------------------------------------------------------------
>
>                 Key: JBAS-3720
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3720
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service, Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> For each SSO entry, their should be child node per server where the SSO has been used.  This is different from the current where all the session data for an SSO is in one node. The data map in each child node would hold the session ids of the sessions active on that server.
> This kind of structure avoids most lock contention between different servers.
> Can't do this in 4.0.x as it prevents interoperation with earlier releases.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira