Hi Rajesh,
In stateless session bean container need only a few beans to service
thousands of clients. In stateful session bean pooling does take place by
activation and passivation mechanism. In stateful session beans when client
invokes a method the passivated conversational state is passed into the
bean. So in this case what I feel is since stateless session bean does not
have passivation technique it does n't work if you put maximum initial bean
no to zero. In other case it does activation and provides the instance.
Regards
Anwar
-----Original Message-----
From: RAJESH Subramanian [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 02, 2001 10:37 AM
To: [EMAIL PROTECTED]
Subject: Stateful & Stateless
Hi all
I have a stateless bean and a client app to access the bean's method.When i
keep the max instance of bean and initial no. of bean in pool as 0(zero) and
the client tries to access any method of the bean,client hangs bcos there r
no bean instances in the pool .But when i keep the same setting for stateful
bean ie max instance to be zero and timeout as say 100 sec and make the
client app to access any method,an instance gets created and the client app
gets response from the bean method.Can anyone clarify as to why this is
happening even if max is set to zero.is there any default settings and it
gets overrided in such cases
Rajesh
===========================================================================
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".
