Evan Ireland wrote: > <vendor> > > With Sybase EAServer, the stubs for EJBHome and EJBObject are thread safe. > > It should be noted, however, that trying to access stateful objects from > multiple threads simultaneously can cause problems. For example, two > client threads that use UserTransaction might attempt to access the same > stateful session bean instance within separate transactions (at the same > time). This could result in an INVALID_TRANSACTION system exception for > one of the threads. > > </vendor>
I find the above statement odd for two reasons: 1. Surely, whether the client threads are using user transactions or not, if you attempt to access the same stateful session bean from two client threads simultaneously then you should expect to get an error because EJBs are not allowed to have multiple threads running simultaneously through them and the server is not required (by the spec) to serialize. 2. Surely the error you should get is not specific to TRANSACTIONS? What would happen if using Bean-managed transactions? It is equally invalid to have two threads calling the SFSB but there are no transactions in sight! On the other hand, JBOSS also produced an INVALID_TRANSACTION exception when I accidentally called a SFSB on two threads, so maybe there's something I'm missing? ======================================== Ian McCallion Alexis Systems Limited Romsey, UK Tel: +44 1794 514883 Fax: +44 1794 501692 ======================================== =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
