We are using JBoss 3.2.1. Our application has lengthy transactions that access many entity beans through CMRs. Whenever an entity bean is accessed through a CMR, that bean is locked by JBoss. As a result, we've experienced ApplicationDeadlockException for a number of scenarios in our application.
When an ApplicationDeadlockException occurs, one of the two(or more) entities involved in the deadlock can be identified easily by examining the stack trace. How can I identify the other entities that are involved in the deadlock? Our application is complex enough that it is very difficult to keep track of of the beans involved in a transaction. I have tried using the entity lock monitor and it has been helpful from time to time but not always. Thanks in advance for any help. Stan View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3857935#3857935 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3857935 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
