There are different locks on entity bean Method Lock
The method lock ensures that only one thread of execution at a time can invoke on a given Entity Bean. This is required by the EJB spec. But, this single-threadedness, can be overridden by marking the bean reentrant in its deployment descriptor. Transaction Lock This means that if any method at all is invoked on an Entity Bean within a transaction, no other transaction can have access to this bean until the holding transaction commits or is rolled back. Please check whether your transactions are long. Check whether your access to the entity bean is ordered. If it is still a problem, you can configure your entity bean as instance per transaction which will wipe away deadlock,but you will loose entity bean caching View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861590#3861590 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861590 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
