Hi!
"Keith L. Musser" wrote:
> 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?
This is a known issue with concurrent systems and pessimistic
concurrency schemes (which is what our cache uses). You should either
wait for transaction timeout and retry, or make sure that they are
always used in the same order.
There are plans to make an optimistic concurrency cache which would fix
this, but this will not be done for awhile.
regards,
Rickar
--
Rickard �berg
Email: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
