In my opinion even if stateless session beans are not maintaining any state,
For the duration of the method call execution it is associated with the
caller. So if multiple users are trying to access the same methos then , we
need to queue the calls which will obviously slow down the performance. But
if we have pool then this problem is solved to some extent.
In fact the EJB specs do not speak anything about pooling
Nitin
-----Original Message-----
From: Dave Ford [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 27, 2001 8:58 AM
To: [EMAIL PROTECTED]
Subject: Why pool stateless session beans?
I asked this question once before, but never got a very satisfying answer.
Why not just have one instance? What is the benefit of pooling stateless
session beans?
Dave Ford
Smart Soft - The Java Training Company
http://www.smart-soft.com
===========================================================================
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".
