It trick is to isolate the problem: There are 3 options available.
1) Jakarta DBCP 1.1 2) Database server 3) Problem in code
I did a test with DBCP 1.1 and McKoi.
This test can be done outside Tomcat, so it is easy to isolate the root cause.
I fired off rapidly a number of connections to the server.
To my big surprise the process is hanging when the number of connections exceeds 8.
I will look into this further tomorrow and repeat the same test without DBCP.
That way I can easily check if the problem is in DBCP or the database server.
My bet is that there is a problem in DBCP.
Let you know how it went.
-- John Zoetebier Web site: http://www.transparent.co.nz
On Mon, 24 Nov 2003 22:55:42 -0600, Anthony Presley <[EMAIL PROTECTED]> wrote:
On Tue, 2003-11-25 at 08:15, John Zoetebier wrote:Could this be the problem ? > <parameter> > <name>maxActive</name> > <value>15</value> > </parameter>
This tells JDBC that the maximum number of connection to be borrowed at any point in time is 15 Increase it to 1000 and test again.
I moved it to 1000, and maxIdle to 100, and get the same errors.
--Anthony
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
