Probably, but the deadlock thread dump is needed to be sure.
--
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
Joao Clemente wrote:
I'm trying to use the following pattern to recover my ejb's after a
failover:
Each EJB checks the need for recovery inside "ejbActivate()".
If there is a need to recover, it eventually calls another EJB to get some
value.
I'm facing a deadlock situation here where I believe that it should appear a
"concurrent calls on stateful beans" exception instead:
EJB1 activates. He needs to recover and needs to call ejb2 to have a certain
value.
EJB2 is passivated so EJB2 activates. He also needs to recover and needs a
value that is in ejb1.
I find a deadlock occuring here, where I was expecting to obtain an
exception ("concurrent calls on stateful beans").
Using this pattern with methods other than ejbActivate we get that
exception, so shouldn't it occur here aswell?
ejb1 {
ejbActivate() {
ejb2.someMethod()
}
}
ejb2 {
ejbActivate() {
ejb1.someMethod()
}
}
-------------------------------------------------------
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
