I'm using proxool java connection pool (version 0.9.1). Everything works fine till I reach the maximum connection count. If the maximum connection count is reached proxool immediately throws an SQLExcepion
:
java.sql.SQLException: Couldn't get connection because we are at maximum
connection count (n/n) and there are none available
Of course instead of n
the maximum connection count is shown.
Why is proxool throwing an SQLException
immediately instead of waiting for an available connection? Not forever of course, but a configurable timeout would be great.
I don't know if it important, but I'm using proxool in a Tomcat J2EE application. Parameters of proxool are defined in context.xml
and I'm using Proxool DataSource Support.