Default optimistic locking configuration leads to inconsistency --------------------------------------------------------------- Key: ISPN-3655 URL: https://issues.jboss.org/browse/ISPN-3655 Project: Infinispan Issue Type: Bug Components: Configuration, Locking and Concurrency, Transactions Affects Versions: 5.3.0.Final, 6.0.0.CR1 Reporter: Galder Zamarreño Assignee: Galder Zamarreño Priority: Blocker Labels: 620 Fix For: 6.0.0.CR2, 6.0.0.Final Infinispan transactional caches are configured with optimistic locking by default. Without extra configuration (REPETEABLE_READ + writeSkews), concurrent replace() calls will return true under contention and transactions will commit. Under contention, even if replace() returns true for multiple resources, it should rollback all except one transaction. When transactional optimistic locking is enabled (default), it should enable all options required to make this scenarios correct.