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 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 ??) - did you wait this long when you were checking Obviously when you stop Tomcat, the whole JRE gets shutdown so what you've seen there is correct "Eric Pr�vost" wrote in message news:[EMAIL PROTECTED] > 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: > > > > > validationQuery > select getdate() > > > maxWait > 5000 > > > maxActive > 50 > > > password > myPassword > > > url > jdbc:microsoft:sqlserver://myserver;DatabaseName=intranet > > > driverClassName > com.microsoft.jdbc.sqlserver.SQLServerDriver > > > maxIdle > 30 > > > username > MyUsername > > > removeAbandoned > true > > > removeAbandonedTimeout > 60 > > > factory > org.apache.commons.dbcp.BasicDataSourceFactory > > > > > 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 removeAbandoned parameter not supposed to take care of these connections??? > > Thank you > > Eric Pr�vost > > > > --------------------------------- > L�che-vitrine ou l�che-�cran ? Yahoo! Magasinage. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------- L�che-vitrine ou l�che-�cran ? Yahoo! Magasinage.
