commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arie (JIRA)" <j...@apache.org>
Subject [jira] Created: (DBCP-248) setting maxWait does not work as expected
Date Tue, 13 Nov 2007 01:17:50 GMT
setting maxWait does not work as expected
-----------------------------------------

                 Key: DBCP-248
                 URL: https://issues.apache.org/jira/browse/DBCP-248
             Project: Commons Dbcp
          Issue Type: Improvement
            Reporter: Arie


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