Hi all,
I've got a program that gets a reference to the home interface of an
stateless session bean, and then starts several threads. Each of them
invokes a create, thus getting a reference to an EJB, and trough that
reference invokes a method of the remote interface. The problem is that
my application server (NetDynamics) serializes method calls, so I get no
benefit from concurrent calls to the EJB.
As far as I know, in the case of an stateless session bean, the
instance actually executing the method is selected at the time the
client invokes the method, so the container may choose from a pool of
ready-to-execute instances, as they are all equivalent. In this case I
see no need of serializing calls, unless you have only ONE instance of
your EJB attending all the requests (!?!?!?!)
The EJB specification states that a single instance of an EJB cannot
receive concurrent calls, and that the container must serialize calls,
but I understand that this is the desired behaviour in case of a program
invoking methods on an stateful session bean, not in the case of
invoking methods on stateless session beans...
Am I right? Is NetDynamics doing right according to the EJB specs?
If yes... how could I achieve concurrency on calls on an stateless
session bean?
Greetings
Jose
===========================================================================
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".
