Hello:
I have been trying to understand the cause of this deadlock exception in
my code, but haven't succeeded. How can I get more information on
understanding the cause of this particular deadlock? I'm stuck. The
only thing that strikes me as "different" in my code is as follows:
Multiple threads execute code that looks like
TopicManager (Stateful Session Bean: pk="X") calls
Exchange (Stateless Session Bean) calls
TopicManager (Stateful Session Bean: pk="Y")
Each thread creates its own session bean. Should this be a problem? Is
it illegal for a stateful session bean to access another stateful
session bean with a different key?
Thanks,
Vidur
Orion 1.1.37 console output:
Transaction was rolled back: thread 9 is waiting for resource session
session 4 held by thread 11 in transaction [Transaction
2f:1:0:0:0:0:0:0:0:e0:0:e0:c1:92:28:36] who is waiting for resource
session session 25 held by thread 9 in transaction [Transaction
32:1:0:0:0:0:0:0:0:e0:0:e0:c1:92:29:8b]; nested exception is:
com.evermind.server.DeadlockException: thread 9 is waiting for
resource
session session 4 held by thread 11 in transaction [Transaction
2f:1:0:0:0:0:0:0
:0:e0:0:e0:c1:92:28:36] who is waiting for resource session session 25
held by thread 9 in transaction [Transaction
32:1:0:0:0:0:0:0:0:e0:0:e0:c1:92:29:8b]
Transaction was rolled back: Deadlock detected:thread 9 is waiting for
resource session session 4 held by thread 11 in transaction [Transaction
2f:1:0:0:0:0:0:0:0:e0:0:e0:c1:92:28:36] who is waiting for resource
session session 25 held by thread 9 in transaction [Transaction
32:1:0:0:0:
0:0:0:0:e0:0:e0:c1:92:29:8b]; nested exception is:
com.evermind.server.DeadlockException: Deadlock detected: thread
9 is waiting for resource session session 4 held by thread 11 in
transaction [Transaction 2f:1:0:0:0:0:0:0:0:e0:0:e0:c1:92:28:36] who is
waiting for resource session session 25 held by thread 9 in transaction
[Transaction 32:1:0:0:0:0:0:0:0:e0:0:e0:c1:92:29:8b]
