The feature you describe is currently not available. The evic thread currently has currently 3 functions: - remove invalid objects (failing validation test) - remove old objects (to prevent timeouts) - ensure minimum capacity
You ask for something new. Slowly reduce the number of objects until the minimum is reached. This can be usefull in some cases, I imagine...
A note on the pool wiki or a bugzilla enhancement issue will make sure we remember this. A patch will help even more ;-)
-- Dirk
David Rosenstark wrote:
We have a question about the implementation of the genericobjectpool. How can we configure the pool to allows us to grow beyond the min number defined and only remove down to the min number and not past when idle? The code of evict wipes out all the objects and creates new objects (up to the min defined) when they have been idle as opposed to just destroying all the objects above the minimum.
Thanks, David
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
