tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <>
Subject Re: JDBC connection pool memory leak
Date Thu, 03 Jan 2013 21:27:11 GMT

did you try to reproduce it with tomcat-jdbc (in a simple test without
tomee or any other framework)?

i wonder if it is linked to tomee or tomcat-jdbc directly (or mysql
since derby seems fine)

any more info or even a test reproducing the issue (in a reasonnable
time) would be great.

Romain Manni-Bucau
Twitter: @rmannibucau

2013/1/3 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 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 working fine for me, but I think I'm experiencing memory
> leaks that are possibly caused by Google Calendar API's use of
> threadlocal/etc... No need to discuss that here in this thread.
> On Thu, Jan 3, 2013 at 1:54 PM, Bjorn Danielsson <
>> wrote:
>> It doesn't matter if I use Eclipselink instead of OpenJPA.
>> But the memory leak goes away if I change the database from Mysql
>> to embedded Derby, so I assume there is some quirkiness in the
>> Mysql driver that is involved.

View raw message