Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-3655

Default optimistic locking configuration leads to inconsistency

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Blocker Blocker
    • None
    • 5.3.0.Final, 6.0.0.Final
    • Configuration, Transactions

      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.

              rh-ee-galder Galder Zamarreño
              rh-ee-galder Galder Zamarreño
              Archiver:
              rhn-support-adongare Amol Dongare

                Created:
                Updated:
                Resolved:
                Archived: