Session stateful are designed to communicate with one and only one client,
because they keep a conversational state with it.
So, an instance shouldn't be accessed by several differents clients. If you
don't need conversational state, use stateless bean.
SAINT-MARTIN Cecile
[EMAIL PROTECTED]
> -----Message d'origine-----
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]De la part de
> Boris Garbuzov
> Envoye : mardi 19 juin 2001 23:19
> A : [EMAIL PROTECTED]
> Objet : [JBoss-user] General EJB question. no concurrent calls on
> stateful beans
>
>
> In my SomeRemote interface I have a method operating on peer:
> void minus (SomeRemote other) throws RemoteException;
> It works fine on a different instance
> myRemote.minus (otherRemote);
> but fails on the same
> myRemote.minus (myRemote);
> java.rmi.ServerException: RemoteException occurred in server
> thread; nested exception is:
> java.rmi.ServerException: Transaction rolled
> back:java.rmi.RemoteException: Application Error: no
> concurrent calls on stateful beans
> I think, I can get around, but generally it is hard. For
> instance, if having remote equals method
> the client application should watch not to call it with the same instance?
>
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
