[
https://issues.apache.org/jira/browse/POOL-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Thomas updated POOL-104:
-----------------------------
Issue Type: Improvement (was: Bug)
As previously noted, the behaviour described is violating the contract which is
clearly set out in the javadocs.
I'm not convinced this can be done in a generic way by the pool and am tempted
to resolve this as WONTFIX. Leaving open for now in case someone wants to take
a crack at providing a patch for this.
> Incorrect behavior for returnObject function.
> ---------------------------------------------
>
> Key: POOL-104
> URL: https://issues.apache.org/jira/browse/POOL-104
> Project: Commons Pool
> Issue Type: Improvement
> Affects Versions: 1.3
> Environment: Windows XP + Eclipse3.2 + JDK1.5
> Reporter: Phenix Huang
> Fix For: 3.0
>
>
> Bussiness Needs
> I want to implement a special pool which can restore the active item
> automatically after over time. After the item had been restored by the pool,
> if client still return the object to pool(client still keep the reference
> thought the object had been passative) , the issue will occurs.
> Test Case :
> 1. Client borrow an object from pool.
> 2. Client return the object to the pool. The active num will substract 1 and
> idle num will plus 1.
> 3. If the client return the same object to the pool many times, the active
> num might be negative.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
