[DBCP-291] setting maxWait does not work as expected

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.3
• Assignee: Unassigned
• Reporter: Arie
• Created: 13/Nov/07 01:17
• Updated: 15/Feb/10 02:23
• Resolved: 24/Dec/09 20:13

Description

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.