[jboss-jira] [JBoss JIRA] Updated: (JBAS-3864) HttpSession replication does not always retry if replication fails
[ http://jira.jboss.com/jira/browse/JBAS-3864?page=all ]
Brian Stansberry updated JBAS-3864:
-----------------------------------
Fix Version/s: JBossAS-4.2.1.CR1
(was: JBossAS-4.2.0.CR1)
Deferring this, as it's a bit more complicated than I thought. JBossCacheWrapper
already retries the cache operations, but another likely place problems can occur is on tx
commit, as that's when replication happens. Need to examine the locations of tx commit
(e.g. BatchReplicationClusteredSessionValve, used with FIELD repl).
HttpSession replication does not always retry if replication fails
------------------------------------------------------------------
Key: JBAS-3864
URL: http://jira.jboss.com/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
Assigned To: Brian Stansberry
Fix For: JBossAS-4.2.1.CR1
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira