It means draw the sequence diagram for the workflow in question, including the transactional and method level locks for two threads that cause the deadlock scenario. If the transaction attributes allow for sequences that access a given beanX which access beanY using a different transaction then you have potential for deadlock.

--
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx

Davide Pozza wrote:

Hi Alexey,
On the previous post you say:

Some threads are accessing the same set of beans in different order.


Many times reading other posts or the JBoss documentation, I've found this phrase, but 
I can't understand it very well...
What's the meaning of the "entity beans ordered access" (see "JBoss Administration and 
Development 2nd ed." pag 208) ?

Thanks in advance

Davide




------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to