> From: Felix Schumacher [mailto:felix.schumac...@internetallee.de] > Subject: Re: Tomcat JDBC Pool memory leak when using StatementFinalizer interceptor
> Am 11.07.2018 um 16:22 schrieb Martin Knoblauch: > > Now it might be, that we are just using the StatementFinalizer in a wrong > > manner. And what we see is expected behavior. Below is our pool > > configuration. Maybe something is just missing :-) > The docs in the interceptor says one has to call close on the > connection, that the statements created. Does your application call > close on the connection? This section of the doc includes a decent model that your webapp code should be following: http://tomcat.apache.org/tomcat-8.0-doc/jndi-datasource-examples-howto.html# Random_Connection_Closed_Exceptions Proper use of a finally block is critical. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
smime.p7s
Description: S/MIME cryptographic signature