-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hop,
On 8/20/2009 11:17 AM, Pham, Hop wrote: > I'm new to this users list. I think that JNDI resource management > (i.e., datasource) is JEE app server domain, and remains available > while Tomcat up by design so that it can be shared across multiple > applications. The original thread referenced in the OP (see the archives, Mohammed gave a link to the original thread) was talking about JNDI DataSources defined in the webapp's context.xml, so they are webapp-specific. In this case, it's appropriate for the webapp to close them down since Tomcat doesn't bother to do it. > Your DBAs may complain about the > number of open connections to the databases, but they are shared > resources, and does not take up much CPU utilization on both database > servers and application servers to keep connections open. Actually, many databases have significant resources allocated on the server side for a connection, even when it's not really being used by the client. Your DBA probably has a reason to complain about wasted resources :) Fortunately, production webapps are rarely restarted.... right? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqO4B0ACgkQ9CaO5/Lv0PAWPQCeLU1BPxwiOLR+GoDBHm1Qgn+U Ez4Anjr9Un0wwdUGoPVk4VxOUkFwSfU2 =5/eE -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
