There is no way to currently block a request when the pool size is at its maximum. This is a behavior we should support so I will add a StrictMaximumSize flag to the instance pool configuration that when set to true will block requests when the pool is at its MaximumSize value.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "jeff andrews" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, December 27, 2001 11:41 AM Subject: RE: [JBoss-dev] JBOSS EJB Container Bug ?! > And since I'm really more interested in the use of JBoss for promoting > deployment of our application's solutions on it for our clients (for > obviouse reasons, especially cost and ease of use), is there a way to turn > this current (extended) concurrent JBoss handling off, and rather allow > additional requests (to the available instances within a pool) to wait until > (freed) bean instances are returned back to the pool..? > Or is the only way for me to currently address it if via modifying the > org.jboss.ejb.plugins.AbstractInstancePool.get() method that you have > outlined below. If so, is there other methods that I should also be > modifying, in order to insure that all bean's container types are behaving > the same? > > Appreciate very much your thoughts and feedbacks. Thanks allot in advance. > > Regards; > Jeff. > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
