We too have _exactly_ the same problem.  In our case we even suspect that the 
condition for a deadlock is not present.  Two resources does not seem to be 
reserved in opposite order.  The exception is triggered when a message bean 
eats consequtive events from an event queue.  Is it possible that deadlock can 
occur when two identical (message)beans run the identical piece of code on 
identical events???


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

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


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to