DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24057>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24057 The borrowed object isn't destroyed if the number of maxActive objects is 0. Summary: The borrowed object isn't destroyed if the number of maxActive objects is 0. Product: Commons Version: 1.1 Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: Other Component: Pool AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The borrowed object isn't destroyed if the number of maxActive objects is 0. I am applying two 2 parches that fix this bug. The first one is related to GenericObjectPool.returnObject(Object obj). This method doesn't check the value of maxActive when determine should be destroyed the returned object. The second one is related to TestGenericObjectPool.testZeroMaxActive(). The unit test doesn't check the number of idle objects after returned the borrowed object. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
