On Wed, 12 Jan 2000 09:06:20 -0800, Assaf Arkin <[EMAIL PROTECTED]> wrote:
>I would recommend keeping it stateless, and trying to figure out how the
>server could handle the load better.
>
>Stateless session beans are more efficient due to this recycling
>implementation. As I said, an EJB server is supposed to handle 500
>clients with 50 sessions. If you're using stateful you will need 500
>sessions for 500 clients, might be more than what your server wants to
>handle.
The server may keep only 50 session beans in his pool. It will use
the passivation to store a session while it is not used and then will
activate it back when that client make a new call.
I agree that using stateless session is a better choice.
Also the server should not create more sessions than what you configured
it to be in the pool. Each session might use a limited resource (Database
connection for example) and trying to use more resource than available might
crash the system or introduce some failures.
Benoit Tremblay (Clea informatique)
at Ericsson Research Canada
===========================================================================
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".
