Hi Brian,
Examples can be found here:
http://svn.apache.org/repos/asf/jakarta/commons/proper/dbcp/trunk/doc/
If you are creating a BasicDataSource yourself then you need to keep it
in a static variable somewhere. You create it once and only close the
datasource when your application is
Ding Ding Ding. We have a winner. That is exactly what I am doing
wrong. A new BasicDataSource is created every time a Java Bean is
called. I guess that also explains why I am seeing 60 - 100 active
connections in netstat when the maxActive value was set to 32.
I will look into using
The key to returning connections to the connection pool is to call
close() on the *connection* itself. The most common way people get
themselves in trouble is to skip this somehow (perhaps because an
exception is thrown).
To avoid that sort of problem, I tend to use an idiom like this for
JDBC
:[EMAIL PROTECTED]
Sent: Thursday, July 14, 2005 5:10 PM
To: Jakarta Commons Users List; [EMAIL PROTECTED]
Subject: Re: [DBCP] Anther lame pool exhausted exception question
The key to returning connections to the connection pool is to call
close() on the *connection* itself. The most common way
