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

A write operation with the SKIP_LOCKING flag can roll back the transaction

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: New (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 7.0.3.Final, 7.1.0.Beta1
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None

      Description

      When a write operation has the SKIP_LOCKING flag, it does not send a LockControlCommand to the primary owner, but it can send a ClusteredGetCommand with acquireRemoteLocks=true instead. The ClusteredGetCommmand will then execute a LockControlCommand with the origin not set properly, and TxInterceptor will roll back the transaction because the originator (null) appears to have left the cluster.

        Attachments

          Activity

            People

            Assignee:
            dan.berindei Dan Berindei
            Reporter:
            dan.berindei Dan Berindei
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: