I have an application, in which every client access is done through a
Stateful Session bean, which internally manages the Entity beans
(Session Facade pattern).
Every single method of my session bean is marked as "Requires" a
transaction. I realize that this can be a performance hit when it's used
unnecessarily. However, I did NOT think that it could lead to deadlock
problems! Nowhere do I explicitly create transactions, and no
transactions are long-lived (between session bean calls). I THOUGHT
(evidently incorrectly) that where concurrent threads need access to the
same entity beans, they would be serialized in time.
However, instead, I'm getting fairly frequent deadlocks, a total
surprise to me.
Is there a nice way to handle this, or an easy way to debug it? Or is
this going to be a nightmare to fix?
Here's to hoping the "Magic of EJB" will again come to my rescue...
Bryan
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
