JBoss itself (the appserver) uses random sleeps and retries (up to 5 times). Unless you have distributed deadlock detection, this is the only way to recover from deadlocks. How to avoid this ? Work on separate data sets in different nodes, e.g. node1 works on data 1-10, node2 on 11-20, node 3 on 21-30 etc. Sometimes this is easy to implement, e.g. in HTTP session replication you can enable session stickiness.
Bela View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3855155#3855155 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3855155 ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
