I finally closed this bug. Now connection requests are queued internally
till the free connections reappear in the pool. Connection requests waiting
for too long (30 sec - hardcoded) will timeout and throw an exception.
Changes are in CVS and will be included in the 10/04 nightly build. This
has NOT been thoroughly tested yet. So unless you are willing to
participate in testing, I recommend waiting for a week or so till we iron
out any possible problems.
Andrus
At 05:22 PM 9/19/2002 +0200, Branko Kannenberg wrote:
>Hi there !
>
>I have a question about connection pooling implemented by cayenne:
>If I set maxconnections to 10 and try to open 11 connections I get an
>exception that the pool cannot open more connections.
>
>Other Poolmanager also have the possibility to let the requester of the new
>connection wait until one connection from the pool gets free again.
>Would this be possible with cayenne?
>It is not so easy to estimate the number of max connections that will be
>used.
>So it would be nice if the application would not stop with an exception if on
>some rare occasion one connection too much is requested.
>
>Ciao, Branko.
This archive was generated by hypermail 2.0.0 : Fri Oct 04 2002 - 02:26:29 EDT