[
https://issues.apache.org/jira/browse/POOL-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17653706#comment-17653706
]
Phil Steitz commented on POOL-401:
----------------------------------
It looks to me that at least as of 2.11.1 reuseCapacity is called on each
activation of invalidateObject in GKOP, so if the freed capacity should be
added to the most heavily loaded pool. Could be I am missing something. A
unit test showing starvation would help.
> GKOP invalidateObject should make capacity available to all keyed pools
> -----------------------------------------------------------------------
>
> Key: POOL-401
> URL: https://issues.apache.org/jira/browse/POOL-401
> Project: Commons Pool
> Issue Type: Bug
> Reporter: Phil Steitz
> Priority: Major
>
> GKOP invalidateObject currently only creates and adds objects if there are
> borrowers waiting for the keyed pool that the instance being invalidated came
> from. If there are no take waiters on that pool, or there is a more heavily
> loaded pool, the (total) capacity should be reused in a different pool.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
