Hi,
I'm using Tomcat 5.0.18 on Linux. My database server is Microsoft SQL Server 2000.
I'm using Microsoft's JDBC driver. This is my data source definition in server.xml:
Resource name=jdbc/intranet type=javax.sql.DataSource/
ResourceParams name=jdbc/intranet
parameter
Hi
If I've understood things correctly
removeAbandoned should enable recovery of 'lost' connections - ie your
webApp dies without cleanly releaseing the Connection object, so having
removeAbandoned on tells the container to keep an eye on things
You've also got the timeout set to 60 (secs ??) -
I did my tests yesterday, and the connections was still alive this morning... I also
tested 5 seconds before.
SMaric [EMAIL PROTECTED] wrote:Hi
If I've understood things correctly
removeAbandoned should enable recovery of 'lost' connections - ie your
webApp dies without cleanly releaseing the
Hi!
Eric Prévost wrote:
I'm using Tomcat 5.0.18 on Linux. My database server is Microsoft SQL Server 2000.
I'm using Microsoft's JDBC driver.
When I stress-test my application with JMeter, I can see over 80 connections on my
database server, and they are not
released until I stop tomcat... Is
When you say 'the connections was still alive this morning'
How are you testing for connections being abandoned
Also your
maxActive = 50//doesn't this mean you shouldn't get more tahn
50 connections from the pool
if this is true ( working) then HOW do you know that the 80
There is only one application on this tomcat server... It's easy to identify these
connections on SQL server. Also, there is no explicit database connection in the
application code: it all pass through JNDI.
I also tried to increase my maxActive setting to 100. It didn't change anything.
I
