It is not requried to close ResultSets, Statements, etc if you close the
connection. (I think) The spec says if you close a connection - all
associated resources for that connection will also be closed.
If you are using a pool - the pool manager *should* be obeying this
principal too.
On Tue, 27 Aug 2002, Tim Funk wrote:
Date: Tue, 27 Aug 2002 12:03:18 -0400
From: Tim Funk [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: Re: Does closing a Connection variable and setting it to null
close all of the
Per the javax.sql javadocs...
When a Connection is closed it closes any open Statements.
When a Statement is closed, it closes any open ResultSets.
If you just dereference a connection (non connection pool) when the
Connection is GC'd it is closed.
If you use DBCP 1.0 as your connection pool
