[infinispan-dev] ISPN-2164 Why does a conditional remove (on it's own), end up with a write skew check?

Hi, Re: https://issues.jboss.org/browse/ISPN-2164 and https://github.com/infinispan/infinispan/pull/1221 It could be argued that a remove, regardless of whether it's conditional or not, should not need to have the need for a write skew check, unless there's really been a read before. IOW, the test now passes because the commit throws an exception in 4 out of 5 threads. But, the test could/should maybe work in such way that no exception was thrown and 4 out of 5 invocations returned false to the checks made (conditional remove returns false, or normal remove returns null). Cheers, -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache