A write operation with the SKIP_LOCKING flag can roll back the transaction -------------------------------------------------------------------------- Key: ISPN-5163 URL: https://issues.jboss.org/browse/ISPN-5163 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 7.0.3.Final, 7.1.0.Beta1 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 8.2.0.Alpha1 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.