DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=39314>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39314 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2006-04-15 22:01 ------- First, there is no "pool size" setting in GenericObjectPool. This bug report is based on the incorrect assumption that there is such a thing. There are maxActive and maxIdle settings but they are not the same thing as the "pool size". (In reply to comment #5) > Strange thing is, if poolsize in the example code is 3 the test runs fine, but > with a poolsize of 20 the pool grows forever. Re-read comment #4, with the above statement you've just proven my point. GenericObjectPool has a default maxIdle setting of 8. You'll find your test code seems to work with a maxActive up to and including 7. From 8 and above you'll see the behavior you are incorrectly claiming to be a bug. If you set the maxIdle to a negative value, there will be no limit on the number of idle objects and you'll basically get your desired "pool size" behavior. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
