Return-Path: 
 <users-return-199988-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org>
Delivered-To: apmail-tomcat-users-archive@www.apache.org
Received: (qmail 10017 invoked from network); 5 Aug 2009 20:34:49 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 5 Aug 2009 20:34:49 -0000
Received: (qmail 42436 invoked by uid 500); 5 Aug 2009 20:34:52 -0000
Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org
Received: (qmail 42402 invoked by uid 500); 5 Aug 2009 20:34:52 -0000
Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@tomcat.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@tomcat.apache.org>
List-Post: <mailto:users@tomcat.apache.org>
List-Id: <users.tomcat.apache.org>
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Delivered-To: mailing list users@tomcat.apache.org
Received: (qmail 42391 invoked by uid 99); 5 Aug 2009 20:34:52 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Aug 2009 20:34:52 +0000
X-ASF-Spam-Status: No, hits=2.2 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: local policy)
Received: from [72.22.94.67] (HELO virtual.halosg.com) (72.22.94.67)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Aug 2009 20:34:42 +0000
Received: (qmail 9222 invoked from network); 5 Aug 2009 15:34:21 -0500
Received: from 38-171-19-72.skybeam.com (HELO ?192.168.1.42?) (72.19.171.38)
  by halosg.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
 5 Aug 2009 15:34:21 -0500
Message-ID: <4A79ECB4.20407@hanik.com>
Date: Wed, 05 Aug 2009 14:33:56 -0600
From: Filip Hanik - Dev Lists <devlists@hanik.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Lightning/1.0pre
 Thunderbird/3.0b2
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Right way to close database connection pool
References: <4A79B6BD.10302@gmail.com> <4A79BBC1.9060402@hanik.com>
 <4A79C2EC.7040305@christopherschultz.net>
In-Reply-To: <4A79C2EC.7040305@christopherschultz.net>
Content-Type: multipart/alternative;
 boundary="------------050307000207060005090807"
X-Virus-Checked: Checked by ClamAV on apache.org

--------------050307000207060005090807
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 08/05/2009 11:35 AM, Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Filip,
>
> On 8/5/2009 1:05 PM, Filip Hanik - Dev Lists wrote:
>    
>> you would need to listen for context destroyed, and cast the datasource
>> to call close() on it
>>      
>
> When Tomcat re-deploys an application, is the existing DataSource
> trashed and re-created? When that happens, are the old connections
> closed? The OP's comments suggest that the old connections are not being
> closed. Is this expected behavior?
>
> Why are Tomcat-created, webapp-specific (that is,<Resource>s from
> META-INF/context.xml) DataSources not cleaned-up after web application
> un-deployment? It would seem that those resources are not applicable to
> any other webapp (because they came from a specific webapp's
> configuration) and should be torn-down during an undeployment.
>
> Am I missing a use case where this makes sense?
>    
nope, its a missing feature.

Filip
> Thanks,
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkp5wuwACgkQ9CaO5/Lv0PC67wCgmaWYuITuwNaoE/Qc3oHuiinp
> 8+wAnjjHV3WTGF3uq4EhbVsUWLtJpFJ4
> =Q63e
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>    


--------------050307000207060005090807--