It's part of the "session bean component contract" (6.11.6)
Non-reentrant instances
The container must ensure that only one thread can be executing an instance
at any time. If a client request arrives for an instance while the instance
is executing another request, the container must throw the
java.rmi.RemoteException to the second request.
Note that a session object is intended to support only a single client.
Therefore, it would be an application error if two clients attempted to
invoke the same session object.
One implication of this rule is that an application cannot make loopback
calls to a session bean instance.
Wim
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Nortje, Andrew
> Sent: donderdag 4 januari 2001 21:29
> To: 'jBoss'
> Subject: [jBoss-User] Stateful Session Bean Call Back
>
>
> I have two statful session beans A and B, running in the same JVM
>
> A calls B and passes a reference to itself to B ( to get the remote
> interface of A I use ctx.getEJBObject() )
>
> B then calls back to A using the remote reference it was passed.
>
> Am I not allowed to do this? jBoss throws the following
> Exception which
> indicates I can't. Is this the EJB spec?
>
> [UniteItDotCom] java.rmi.RemoteException: Application Error:
> no concurrent
> calls on stateful beans
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
