I have a SessionBean which performs a search on Entity Beans. The
sequence in which the search accesses the Entity Beans depends on call
arguments to the session bean.
When I invoke the session bean from multiple clients, I get deadlock.
This appears to be because search 1 assesses entity A first, then entity
B. Search 2, however, acesses entity B first, then entity A.
So if the timing is just wrong, both searches get the first entity, but
cannot get the second, since it's locked by the other search.
Is there a way to set up jboss.xml to prevent this from happening?
Keith L. Musser
Integrated Dynamics, Inc.
812-371-7777
email: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
