"bela" wrote : #1 exists() doesn't acquire a lock, use get().

We tried the top-level if with both and exist and get to see if it made any 
difference before I posted, because we thought this might be the case.   Thanks 
for (correctly) pointing back to the Javadoc.

"bela" wrote : #2: you try to update the same data on 3 nodes concurrently. 
Because you use REPL_SYNC...This is a typical distributed deadlock.

Thanks for the distributed deadlock explanation.  I knew that there was 
something I was missing.  For us, the locking is not so important (so we will 
probably not use transactions).

What are the solutions for this type of problem?  Random sleep times before 
retrying if a timeout occurs?  What about a master node that hands out 
locks/blocks when called?  It seems like there would be a pretty standard set 
of possibilities when this type of situation is encountered.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3855017#3855017

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3855017


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to