Bug reported at https://issues.apache.org/bugzilla/show_bug.cgi?id=54732
Due to another bug in TomEE, StatementCache is always enabled. That bug
is reported here: https://issues.apache.org/jira/browse/TOMEE-837
Thanks for your help
On 20/03/2013 7:28 AM, Felix Schumacher wrote:
Am 19.03.2013
Bug reported at https://issues.apache.org/bugzilla/show_bug.cgi?id=54732
Due to another bug in TomEE, StatementCache is always enabled. That bug
is reported here: https://issues.apache.org/jira/browse/TOMEE-837
Thanks for your help
On 20/03/2013 7:28 AM, Felix Schumacher wrote:
Am 19.03.2013
Am 19.03.2013 22:20, schrieb Bertrand Guay-Paquet:
On 19/03/2013 5:05 PM, Felix Schumacher wrote:
Have you looked at
http://grokbase.com/t/openejb/users/13135d2a0v/jdbc-connection-pool-memory-leak
? It seems like your problem. Regards Felix
Indeed, this is extremely similar to my issue. Thank
On 19/03/2013 5:05 PM, Felix Schumacher wrote:
Have you looked at
http://grokbase.com/t/openejb/users/13135d2a0v/jdbc-connection-pool-memory-leak
? It seems like your problem. Regards Felix
Indeed, this is extremely similar to my issue. Thanks for sharing this.
It does seem however like the S
Bertrand Guay-Paquet schrieb:
>Hello,
>
>I'm using Tomcat 7.0.34 via TomEE 1.5.1 with MySQL. I noticed a memory
>leak in my web application which uses jdbc connection pooling with
>Tomcat's jdbc-pool.
>
>The com.mysql.jdbc.JDBC4Connection class has a field named
>"openStatements" which holds
Can you post some example of your code? Can you also post your pool's
configuration?
Here is my configuration from tomee.xml. I'm not 100% sure how it maps
to Tomcat values though.
JdbcDriver=com.mysql.jdbc.Driver
JdbcUrl=jdbc:mysql://localhost:3306/DBNAME
UserName=
Password=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bertrand,
On 3/19/13 3:48 PM, Bertrand Guay-Paquet wrote:
> I'm using Tomcat 7.0.34 via TomEE 1.5.1 with MySQL. I noticed a
> memory leak in my web application which uses jdbc connection
> pooling with Tomcat's jdbc-pool.
>
> The com.mysql.jdbc.JDB
Hello,
I'm using Tomcat 7.0.34 via TomEE 1.5.1 with MySQL. I noticed a memory
leak in my web application which uses jdbc connection pooling with
Tomcat's jdbc-pool.
The com.mysql.jdbc.JDBC4Connection class has a field named
"openStatements" which holds, as you can imagine, open sql statement