<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Pedro and thanks for reporting this.<div>Do you have versioning enabled? Otherwise the writeSkewCheck won't be performed at commit time. </div><div>If you do have versioning enabled, may I suggest to take this on the user forums[1] - this way it would be easier for other users that have the same problem to find it.</div><div><br></div><div>[1] <a href="https://community.jboss.org/community/infinispan?view=discussions&start=0">https://community.jboss.org/community/infinispan?view=discussions&start=0</a></div><div><br><div><div>On 24 Jan 2012, at 18:42, Pedro Ruivo wrote:</div><blockquote type="cite"><div>Hi,<br><br>I think I have spotted a problem with the write skew check <br>implementation based on versioning.<br><br>I've made this test to confirm:<br><br>I have a global counter that is incremented concurrently by two <br>different nodes, running ISPN with Repeatable Read with write skew <br>enabled. I expected that each successfully transaction will commit a <br>different value.<br><br>In detail, each node do the following:<br><br>beginTx<br>Integer count = cache.get("counter");<br>count = count + 1;<br>cache.put("counter", count)<br>commitTx<br><br>To avoid errors, I've run this test on two ISPN versions: 5.1.0.CR4 and <br>5.0.1.Final. In 5.0.1.Final, it works as expected. However, on 5.1.0.CR4 <br>I have a lot of repeated values. After a first check at the code, I've <br>the impression that the problem may be due to that the version numbers <br>of the keys for which the write skew check should be run is not sent <br>with the prepare command.<br><br>Cheers,<br>Pedro Ruivo<br>_______________________________________________<br>infinispan-dev mailing list<br><a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/infinispan-dev<br></div></blockquote></div><br></div></body></html>