commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 24057] New: - The borrowed object isn't destroyed if the number of maxActive objects is 0.
Date Thu, 23 Oct 2003 13:23:41 GMT
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: commons-dev@jakarta.apache.org
        ReportedBy: tsvetelin.saykov@rushmore-digital.com


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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message