Actual container implementation is vendor specific; some create new
instance for each client to insure thread-safety; others grab from a pool,
but shifts the state around to give the perception of one-to-one
statefulness. Regardless of the implementation, EJB spec is followed, which
is "EJB is thread safe".
Gene Chuang
Join Kiko.com!
----- Original Message -----
From: "Naveen Chandra" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, December 10, 2000 12:09 PM
Subject: Is EJB Thread Safe ?
> Hi EJBGurus,
>
> Please don't think that it is a silly question to ask here,
> It makes me to understand the EJB implementation bit more clear.
>
> As I understand when the client invokes a create method on the home
> object, the container instantiates the corresponding bean and then
> invokes the beans ejbCreate method.
> Here is my question when thousand clints tries to access the same
> bean at the same time, does the container creates thousand
> of such objects from the abstract factory pattern?
> Or it process all the business methods from the pool like servlets
> doGet, and doPost methods ?
>
> If it creates thousand of such bean objects to process thousand users
> requests
> at a time, then what happens when we declare class variables in the bean.
> Does EJB allows to declare class level variables ?
>
> Thanks in advance,
> Naveen.
>
>
===========================================================================
> 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".
===========================================================================
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".
