I forgot to add that the ejb 1.1 spec does not require that
a container reuse the same instance for subsequent calls.
But the performance of such an implementation would
be questionable ... and hence the pooling.
-krish
> Dave,
>
> As per the EJB 1.1 spec, a container serializes access to each
> session bean instance. In the case of a SLSB, a single instance
> *could* become the bottleneck under heavy loads - say when
> the number of concurrent clients increase.
>
> An alternative is to have a multiple instances of the same SLSB
> service client requests. This is not a contradiction of a SLSB as
> the instance does not hold any state relative to a client. Thus
> multiple instances of a SLSB can serve multiple client requests
> in a multi-threaded way - overcoming the serial access imposed
> by the ejb 1.1 spec.
>
> -krish
>
===========================================================================
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".
