-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
None
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?