[
https://issues.apache.org/jira/browse/POOL-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-109:
-----------------------------
Fix Version/s: 2.0
Improving precision in per-thread timeouts will require more advanced
scheduling than is currently available. Best to wait for JDK source level 1.5.
> setting maxWait does not work as expected
> -----------------------------------------
>
> Key: POOL-109
> URL: https://issues.apache.org/jira/browse/POOL-109
> Project: Commons Pool
> Issue Type: Improvement
> Reporter: Arie
> Fix For: 2.0
>
>
> My expectation was that if maxWait is set to X seconds and there are N
> requests waiting to get a connection (in a case where the pool is bounded and
> all the connection are used) if none of the used connection gets free than
> all N requests will time-out at the same time.
> In reality it seems that 1 request will be timed-out after X seconds the
> second one after 2 * X and the last one after N * X.
> The problem is that getPooledConnectionAndInfo is synchronized (and therefore
> will look all N requests) and only one request will be processed at the time.
> This process includes waiting until freed connection or timed-out (done by
> commons.pool GenericKeyedObjectPool).
> I am not sure why the getPooledConnectionAndInfo has to be synchronized and
> not only the pool creation part.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
