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

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.