[infinispan-issues] [JBoss JIRA] (ISPN-3655) Default optimistic locking configuration leads to inconsistency
[
https://issues.jboss.org/browse/ISPN-3655?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on ISPN-3655:
-----------------------------------------------
Misha H. Ali <mhusnain(a)redhat.com> made a comment on [bug
1024373|https://bugzilla.redhat.com/show_bug.cgi?id=1024373]
Added the flag. Gemma will develop this release note for the GA Release Notes as a
resolved issue.
In the meantime, if someone can point us to a JIRA that tracked this issue originally or
add some CCFR information about this issue, it would be very helpful.
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: jdg620_dm, jdg62GAblocker
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.
--
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