Re: JDBC connection pool memory leak

2013-01-08 Thread Bjorn Danielsson
Update: Confirmed, everything looks good after running 46 hours. I also started a second test yesterday using the same code but Eclipselink instead of OpenJPA. It too looks good after 24 hours. The only instances I could see increasing slowly were objects called compiledICHolderKlass, which I

Re: JDBC connection pool memory leak

2013-01-08 Thread Romain Manni-Bucau
Great! thanks for the feedback. That's really appreciated. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/1/8 Bjorn Danielsson bjorn-apa...@lists.cuspycode.com:

Re: JDBC connection pool memory leak

2013-01-06 Thread Bjorn Danielsson
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

Re: JDBC connection pool memory leak

2013-01-06 Thread Howard W. Smith, Jr.
Well, I thank you both. After this discussion and fix, I just had to download the latest SNAPSHOT of TomEE plus (even though I am using embedded Derby), and web app seems a bit faster 'tonight'. :) On Sun, Jan 6, 2013 at 10:19 AM, Bjorn Danielsson bjorn-apa...@lists.cuspycode.com wrote: Many

Re: JDBC connection pool memory leak

2013-01-04 Thread Bjorn Danielsson
I just reproduced the memory leak in a plain Tomcat 7.0.34, using only JDBC and a Mysql datasource: InitialContext ctx = new InitialContext(); DataSource ds = (DataSource) ctx.lookup(java:/comp/env/jdbc/test); Connection conn = ds.getConnection(); PreparedStatement stmt =

Re: JDBC connection pool memory leak

2013-01-04 Thread Romain Manni-Bucau
Hi, great progress! just to be sure to understand: in a plain tomcat does StatementFinalizer replace stmt.close() to make the leak going away? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github:

Re: JDBC connection pool memory leak

2013-01-04 Thread Bjorn Danielsson
Romain Manni-Bucau rmannibu...@gmail.com wrote: just to be sure to understand: in a plain tomcat does StatementFinalizer replace stmt.close() to make the leak going away? Yes. -- Bjorn Danielsson Cuspy Code AB

Re: JDBC connection pool memory leak

2013-01-04 Thread Romain Manni-Bucau
ok so can you share a sample reproducing the issue 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 Bjorn Danielsson bjorn-apa...@lists.cuspycode.com: Romain

Re: JDBC connection pool memory leak

2013-01-04 Thread Bjorn Danielsson
Hi Romain, I have a tiny tarball with sources and build.xml available here: http://dev.cuspycode.se/public/poolbugtest.tar.gz Look in README.txt for further instructions. I made the example as small as I could, it's very tiny, but there are a few steps to go through since a database needs to be

Re: JDBC connection pool memory leak

2013-01-03 Thread Howard W. Smith, Jr.
Very interesting info here, thanks for sharing. I have been using TomEE since 1.5.1-SNAPSHOT and now 1.5.2-SNAPSHOT. Also, I'm using Apache Derby 10.9.1.0 and Eclipse 2.3.2, and JDBC configured in tomee.xml. Can you share your JDBC config from your tomee.xml and/or context.xml? Apache Derby is