[jboss-jira] [JBoss JIRA] Closed: (JBCACHE-806) Invalidation causes problems with otimistic data versioning and certain edge cases

Invalidation causes problems with otimistic data versioning and certain edge cases ---------------------------------------------------------------------------------- Key: JBCACHE-806 URL: http://jira.jboss.com/jira/browse/JBCACHE-806 Project: JBoss Cache Issue Type: Bug Security Level: Public(Everyone can see) Components: Replication Affects Versions: 1.4.0.SP1 Reporter: Manik Surtani Attachments: OptimisticAsyncInvalidationTest.java, OptimisticSyncInvalidationTest.java Related to JBCACHE-793, but that has more to do with fixing the recommended configurations. From email conversations: Manik >> At the moment, if I do a put() with V1 into CacheA, this sends an invalidation msg to CacheB. If CacheB has V2 already, the invalidation will fail. What you are saying is, this failure should propagate back to CacheA so the put() with V1 will also fail and this will not exist in CacheA's memory. Am I correct? Max >> It wasn't the scenario I had in mind, but this one is probably also relevant. Manik >> Or is the scenario you're trying to paint more like: V2 put into CacheA. CacheB has V1, gets the invalidation msg, and V1 is evicted. Someone now calls a put() on CacheB with V1, and you are afraid this will be written into the cache? This is true, the invalidation back to CacheA will fail, but CacheB will have stale data in the cache. Max >> This is the scenario I had in mind yes.