commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Thomas (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (POOL-155) ObjectPool.invalidateObject(object) should throw an Exception if object is null
Date Sun, 14 Aug 2011 20:12:27 GMT

     [ https://issues.apache.org/jira/browse/POOL-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mark Thomas resolved POOL-155.
------------------------------

    Resolution: Fixed

Pool 2.0.x ensures the following:
- only objects borrowed from the pool may be returned to the pool
- only objects currently borrowed from the pool may be returned to it (borrow, return, return
on the same object will fail)

> ObjectPool.invalidateObject(object) should throw an Exception if object is null
> -------------------------------------------------------------------------------
>
>                 Key: POOL-155
>                 URL: https://issues.apache.org/jira/browse/POOL-155
>             Project: Commons Pool
>          Issue Type: Improvement
>    Affects Versions: 1.0, 1.0.1, 1.1, 1.2, 1.3, 1.4, 1.5, 1.5.1, 1.5.2, 1.5.3, 1.5.4
>            Reporter: Sebb
>             Fix For: 2.0
>
>
> ObjectPool.invalidateObject(object) should throw an Exception if object is null, otherwise
the numActive count can get out of synch.
> It's easy to do this by mistake, see:
> http://markmail.org/thread/ya22ihmghejbfzme
> Also, the documentation for ObjectPool needs to be updated to clarify that invalidateObject
should only be called if the object failed, not the borrow.
> [I'll do this shortly]

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message