Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <7087722.1195495245772.JavaMail.jira@brutus>
Date: Mon, 19 Nov 2007 10:00:45 -0800 (PST)
From: "Arie (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Issue Comment Edited: (POOL-109) setting maxWait does not
 work as expected
In-Reply-To: <6064972.1194916670994.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

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=20

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

 =20
> 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 re=
quests waiting to get a connection (in a case where the pool is bounded and=
=20
> all the connection are used) if none of the used connection gets free tha=
n 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 there=
fore will look all N requests) and only one request will be processed at th=
e time.
> This process includes waiting until freed connection or timed-out (done b=
y commons.pool GenericKeyedObjectPool).
> I am not sure why the getPooledConnectionAndInfo has to be synchronized a=
nd not only the pool creation part.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.