RE: mysql connection pool

That doesn't happen under java. You have to explicitly free/close all resources that are more valuable than memory (file handles, db connections, ...) The finalizer is called by the garbage collector, which in turn can run any time or not even at all (if you don't consume enough memory). >From

RE: mysql connection pool

ok great, but why does the lookup for a datasource always return a new pool instance ? I am running tomcat 4.0.1, maybe that is the problem? hope you can help Hans At 04:13 PM 7/28/2003 +0200, Ralph Einfeldt wrote: That doesn't happen under java. You have to explicitly free/close all resources t

RE: mysql connection pool

om: Hans Wichman [mailto:[EMAIL PROTECTED] > Sent: Monday, July 28, 2003 4:27 PM > To: Tomcat Users List; Tomcat Users List > Subject: RE: mysql connection pool > > ok great, but why does the lookup for a datasource always > return a new pool instance ? > I am running to

RE: mysql connection pool

se, it's not a new instance of the pool, it's the new variable that refers to a single instance of the pool. Just double checking. > -Original Message- > From: Hans Wichman [mailto:[EMAIL PROTECTED] > Sent: Monday, July 28, 2003 9:27 AM > To: Tomcat Users List; To

RE: mysql connection pool

:27 PM > To: Tomcat Users List; Tomcat Users List > Subject: RE: mysql connection pool > > ok great, but why does the lookup for a datasource always > return a new pool instance ? > I am running tomcat 4.0.1, maybe that is the

RE: mysql connection pool

the pool. Just double checking. > -Original Message- > From: Hans Wichman [mailto:[EMAIL PROTECTED] > Sent: Monday, July 28, 2003 9:27 AM > To: Tomcat Users List; Tomcat Users List > Subject: RE: mysql connection pool > > > ok great, but why does the lookup for a dataso

Re: mysql connection pool

I don't know what is going on in this case but this is normal procedure. When you close the connection, you really are (normally) just closing a wrapper to a connection, which, instead of really closing it, just sends it back to the pool. I suspect this is really what is happening. The pools

Re: MySQL-connection pool

Take a look at: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-resources-howto.html About halfway down the page is a section titled 'JDBC Data Sources' Also take a look at: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-datasource-examples-howto.html This page has some specific examples

RE: MySql connection pool difficulties

driverClassName org.gjt.mm.mysql.Driver > -Original Message- > From: Tom O'Neil [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 13, 2003 2:25 PM > To: [EMAIL PROTECTED] > Subject: MySql connection pool difficulties > > > After scouring the

RE: MySql connection pool difficulties

Matt, This is how I got mine working... In Server.xml within url jdbc:mysql://localhost:3306/tigardDB?autoReconnect=true maxActive 100 maxWa

Re: MySql connection pool difficulties

Tom O'Neil wrote: After scouring the mailing list and a few forums, I'm still at a dead end attempting to get MySql connection pooling working with Tomcat. I'm running the following on Windows 2000: Tomcat 4.1.18 MySql 4.0.10 JDK 1.4.1 I've tried using both the MySql 3.0.5 and 2.0.14 drivers. I'

Re: MySql connection pool difficulties

it> cc: Subject: Re: MySql connection pool difficulties 14/02/20