[infinispan-issues] [JBoss JIRA] (ISPN-3655) Default optimistic locking configuration leads to inconsistency

[Galder Zamarreño (JIRA)]

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

Galder Zamarreño updated ISPN-3655:
-----------------------------------

           Status: Closed  (was: Pull Request Sent)
    Fix Version/s:     (was: 6.0.0.Final)
                       (was: 6.0.0.CR2)
       Resolution: Deferred


Deferred to 7.0
                
> 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
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira