We're changing our app so that we can recover the transient parts of our objects so that we can eventually support failover. One of our recovery methods fails with "Application error: no concurrent calls on stateful beans" and we're being unable to trace what is responsible for this behaviour. We are using a single client so there should be only one call, not two. One thing I am thinking is that maybe the server is activating the ejb and at the same time it invokes the recovery method that we wrote.
Maybe one of you has already faced this situation and has suggestions. We're using jboss 3.0.8 ------------------------------------------------------- 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
