[jboss-jira] [JBoss JIRA] Updated: (JBAS-7852) Use distributed locking as a means of detecting need to refresh sessions in the L1 web session cache

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated JBAS-7852:
-----------------------------------

         Assignee: Brian Stansberry
    Fix Version/s: 6.0.0.Final
                       (was: 6.0.0.M4)


> Use distributed locking as a means of detecting need to refresh sessions in the L1 web session cache
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-7852
>                 URL: https://jira.jboss.org/browse/JBAS-7852
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: 6.0.0.Final
>
>
> Use values returned from JBAS-7851 impl as means of detecting a failover situation. If it's a failover, refresh the internal state of the locally stored session (if there is one) from the distributed cache.
> Don't throw away session instances, as external code (e.g. SSOValve) may have refs to them.

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