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 StatementFinalizer Tomcat interceptor
should not be necessary if an application closes its connections,
statements and result sets properly. From what I could see by stepping
in the code, this is the case with MyBatis. The actual source of the
problem really seems to be that Tomcat's jdbc pool swallows calls to
Statement.close() like I showed in my original message.
Regards,
Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
