commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arie (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (POOL-109) setting maxWait does not work as expected
Date Mon, 19 Nov 2007 18:00:45 GMT

    [ https://issues.apache.org/jira/browse/POOL-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543477
] 

aozarov@hotmail.com edited comment on POOL-109 at 11/19/07 10:00 AM:
------------------------------------------------------

Not sure what did you have in your mind but util.concurrent (if needed) is available as concurrent.util
for JDK < 1.5

      was (Author: aozarov@hotmail.com):
    Not sure what did you have in your mind but util.concurrent (if needed) is available as
concurrent.util for JDK < 1.5Regards, Arie Ozarov 

_________________________________________________________________
You keep typing, we keep giving. Download Messenger and join the i’m Initiative now.
http://im.live.com/messenger/im/home/?source=TAGLM

  
> 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.


Mime
View raw message