First, I hope you understand that optimistic locking in 1.2.4 is an ALPHA release and is full of bugs! :)
Optimistic locking in 1.3 has a lot of new fixes which will help solve these issues. The specific problem you see is due to node eviction. A node is evicted, and ongoing transactions try and commit and fail due to incompatible node versioning. This is why you see things improve when you increase the maxNodes setting, because eviction doesn't occur as frequently then. This problem will be solved in future versions of JBossCache and Hibernate when we expose our versioning API to Hibernate and Hibernate pulls version info from the database directly. This will allow for proper validation even after a node has been evicted. For now, there is little I can recommend except: 1) Don't use opt locking in 1.2.4 in production! 2) Increase the maxNodes setting. Or even remove the eviction policy if it is not critical. Or use an LRU eviction policy so nodes that are unlikely to be used again get evicted, minimising the possibility of this happening. Thanks for trying this out though, it is great to see feedback on this. Optimistic locking is a major feature of 1.3 and we'd like to learn as much as we can from what we released in 1.2.4. Cheers, Manik View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3907866#3907866 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3907866 ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
