Many thanks Romain! It looks like the memory leak is gone with the new snapshot. The extra Mysql Statement and ResultSet instances disappeared even without configuring JdbcInterceptors = StatementFinalizer.
But I enabled StatementFinalizer for a longer test. I'll leave it running for a few days just to confirm that the leak is completely plugged. -- Bjorn Danielsson Cuspy Code AB Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > ok, > > with https://issues.apache.org/jira/browse/TOMEE-703 (available > tomorrow on snapshot) > > + > > <Resource id="jdbc/poolbugtest" type="DataSource"> > DataSourceCreator tomcat > JdbcDriver com.mysql.jdbc.Driver > JdbcUrl jdbc:mysql://localhost:3306/poolbugtest > ValidationQuery SELECT * FROM MYTABLE > JtaManaged true > jdbcInterceptors = StatementFinalizer > </Resource> > > it should be better > > can you check it please? > > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > > 2013/1/4 Howard W. Smith, Jr. <smithh032...@gmail.com>: >> Is this possibly related to the following discussion (which was >> coincidentally discussed today as well on tomcat user list) ? >> >> http://tomcat.10.n6.nabble.com/jdbc-pool-Transaction-left-open-by-the-connection-validation-mechanism-td4991758.html
