If you don't want to have more than one instance of the session bean during
the lifetime of the application server up-period then its better to leave
the application server at first place. It is there to provide scalable
solutions rather than restricting scalability.
-----Original Message-----
From: Shomnathprabukm [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 24, 2001 10:54 AM
To: [EMAIL PROTECTED]
Subject: Session Bean Info - WebSphere/Weblogic
For a Stateless Session Bean is there any way where I
can say that only one Client access the bean at any point of time.
I tried setting the MAX/MIN Pool size properties of the bean both to 1.
But it doen't work.
Regards
ShomnathPrabu KM
Infosys
India
===========================================================================
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".
