[jboss-jira] [JBoss JIRA] Updated: (JBAS-3864) HttpSession replication does not always retry if replication fails

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated JBAS-3864:
-----------------------------------

    Fix Version/s: Backlog
                       (was: JBossAS-5.1.0.Beta1)


Move to backlog until when it can be done is clearer; stop just rolling from release to release.

> HttpSession replication does not always retry if replication fails
> ------------------------------------------------------------------
>
>                 Key: JBAS-3864
>                 URL: https://jira.jboss.org/jira/browse/JBAS-3864
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: Backlog
>
>         Attachments: JBAS-3864.Branch_4_2.rev58893.svndiff
>
>
> If replication of a session fails, the session replication layer does not retry.  This leaves the local session map in JBossCacheManager out of sync with the distributed cache.  If there is a failover while the distributed cache is out of sync, the user will see stale data.
> Need to retry a (configurable) X number of times.  If the session still doesn't replicate, need to decide what to do -- i.e. is it too late in the request cycle to throw an exception and return an error to the client?

-- 
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