tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor Urisman <>
Subject Re: Resource management in new Tomcat JDBC connection pool.
Date Wed, 10 Apr 2013 23:52:12 GMT
Thanks, Dan et al.
StatementFinalizer is exactly what I was looking for.  A quick look at
the source
exactly what I needed to know: statements are stashed away and individually
closed on Connection.close().

On Wed, Apr 10, 2013 at 1:26 PM, Bertrand Guay-Paquet <> wrote:

> Hi,
> Have a look at**iqgvj34347z77tnc<>for
a bug in the current Tomcat version and its workaround. This seems to
> affect MySQL primarily.
> Regards,
> Bertrand
> On 10/04/2013 4:05 PM, Igor Urisman wrote:
>> Hello,
>> The new Tomcat 7 JDBC
>> pool<**~fhanik/jdbc-pool/jdbc-pool.**html<>
>> >is
>> quite new and not much has been written on it yet.  Has anyone looked
>> it
>> how well it manages underlying resources, both in java domain and in the
>> database?
>> More specifically, what happens when I call Connection.close()
>> without explicitly first closing statements and result sets that were
>> created via this connection? An un-pooled raw JDBC connection will do the
>> right thing and close underlying resource when closed.  But in a pool
>> setup, connection close() simply returns it to the pool.
>> In an ideal world, a pooled connection proxy will keep track of the
>> underlying resources and release/close them when closed.  But that's known
>> not to have been the case in the past and I didn't find any guarantees of
>> that in the docs for the new pool.  I've been running some tests and I am
>> coming up with surprises.  I don't want yet to post code to this list.
>>   Just a general inquiry for now.
>> Thanks in advance,
>> -Igor.
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.**<>
> For additional commands, e-mail:

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