[
https://issues.apache.org/jira/browse/POOL-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-420:
-----------------------------
Description: This issue was initially reported by Jedis developers against
GenericObjectPool in POOL-418. GenericKeyedObjectPool has the same problem.
If there are no idle instances under the requested key when borrowObject is
invoked, but the pool has capacity to create and the subsequently create fails,
the time spent waiting on the create is not subtracted from the time left to
wait on the pool, leading to wait times longer than the wait time parameter or
configured max wait time. (was: This issue was initially reported by Jedis
developers against GenericObjectPool in POOL-418. GenericKeyedObjectPool has
the same problem. If the pool has capacity )
> The maximum wait time for GenericKeyedObjectPool.borrowObject(*) may exceed
> expectations due to a spurious thread wakeup
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: POOL-420
> URL: https://issues.apache.org/jira/browse/POOL-420
> Project: Commons Pool
> Issue Type: Bug
> Reporter: SunShuai
> Assignee: Gary D. Gregory
> Priority: Minor
> Fix For: 2.12.1, 2.12.2
>
>
> This issue was initially reported by Jedis developers against
> GenericObjectPool in POOL-418. GenericKeyedObjectPool has the same problem.
> If there are no idle instances under the requested key when borrowObject is
> invoked, but the pool has capacity to create and the subsequently create
> fails, the time spent waiting on the create is not subtracted from the time
> left to wait on the pool, leading to wait times longer than the wait time
> parameter or configured max wait time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
