The nature of pessimistic locking may lead to some deadlocks, e.g. check out the DeadlockUnit test case: If tx1 acquires /a/b, then tx2 acquires /1/2, then tx1 tries to acquire /1/2 and tx2 tries to acquire /a/b, that's a deadlock. One of the 2 transactions will time out, therefore rollback its changes, and the other one will succeed. You should be prepared to catch TimeoutExceptions and handle them, e.g. retry,
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878000#3878000 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878000 ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
