tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: Right way to close database connection pool
Date Wed, 05 Aug 2009 17:35:40 GMT
-----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?

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


Mime
View raw message