I understand your point. The solution is to provide an optimistic locking behavior of which Gavin and us have been discussed for a while. This feature has urgency now. :-)
Finally, if it is random deadlock (so your first example above won't work), it will simply timeout and rollback the tx. So another alternative for now is to reduce the LockAcquistionTimeout in JBossCache from default 15s to, say, 3 secs. You will get occasional deply but only randomly, that's the theory. Another point is that this is the problem when you use pessimistic locking under tx. Nothing to do with the cache itself. -Ben View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864878#3864878 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864878 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
