Resending due to my messed up sendmail config... ---------- Forwarded Message ----------
Subject: org.jboss.ejb.plugins.TimedInstancePoolFeeder Date: Fri, 10 May 2002 08:26:11 -0700 From: Jason Dillon <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Why is JBoss3 setup by default to use this feeder policy? I am still working on porting to 3.0 and ran into this and was concered. I had one client come in and call a SLSB and my logs got filled up with bean creation. The default config has a max of 100 for the pool and a 10x increment every 500ms. In my case this SLSB depends on another SLSB... so in the case of a single client coming in I get 200 instances in a few seconds. Why? I looked for another impl of InstancePoolFeeder and could not find one, though I only looked at the javadocs generated for jboss/server. This policy is really lame in my oppinon. Why not just have the pool init to its max size... though I would suggest that isn't really what we want to be doing. Is anyone working on making this more intelligent? Just from looking over the InstancePool interface it looks like there is no easy way to determine how big the pool is vs. how many objects have been handed out... unless getCurrentSize() returns the adujsted size. But size the protocol is get() and free() I am guessing that there is still internal state for the pool tracking objects which have been handed out. It would be nice to have the default feeder grow the pool by n when the current pool has not maxed out but has no more free objects... but that would be much easier to implement from inside of the pool... otherwise the pool will need to expose async events for the feeder to listen to and then react to them by adding or removing elements. Any ways, this seems like very strange behavior for defaults... sure someone might want this, but as far as I can tell the usage is very limited... perhaps only to situations where the incoming client rate is constant durring the period it takes to grow the pool to its max size. So why is this on by default... I don't get how this is useful. It would be much better to have a pluggable policy to tell the pool how to grow and shrink. Am I insane? --jason ------------------------------------------------------- _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
