tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard W. Smith, Jr." <>
Subject Re: JDBC connection pool memory leak
Date Thu, 03 Jan 2013 20:17:29 GMT
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

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.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message