tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pham, Hop" <Hop.P...@USPTO.GOV>
Subject RE: Problem closing datasource when used as JNDI resource
Date Thu, 20 Aug 2009 15:17:29 GMT
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. It is not effective to terminate datasource connections, and
resume connetion pool establishment when a new request for datasource arrives.  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.

thanks,
-hop
________________________________________
From: Mohammed Bin Mahmood [mohammed@sustainlane.com]
Sent: Thursday, August 20, 2009 9:44 AM
To: 'Tomcat Users List'
Subject: RE: Problem closing datasource when used as JNDI resource

Thanks Chris,

But I still do not get my answer yet.

Does anybody have the better way to shut down the data source when started
by tomcat using JNDI resource?
Or is there any configuration we can do so that tomcat closes it
automatically without us doing any workarounds?

Thanks,
Mohammed.
-----Original Message-----
From: Christopher Schultz [mailto:chris@christopherschultz.net]
Sent: Wednesday, August 19, 2009 7:05 PM
To: Tomcat Users List
Subject: Re: Problem closing datasource when used as JNDI resource

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mohammed,

On 8/19/2009 8:25 AM, Mohammed Bin Mahmood wrote:
> When tomcat takes care of creating maintaining datasource, then does it
not
> closes it when server is shut down?

According to Filip's comments on the first thread you mentioned, yes:
the connection pool is not explicitly closed.

> Do we have to close it on our own (the way I do) or is there any better
way
> to do it without external listener?

The best way would be to have Tomcat actually shut-down the DataSource,
since it created it in the first place.

Patches to Tomcat are always welcome :)

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqL/4MACgkQ9CaO5/Lv0PD39QCdEWcriY2WJyRfKDYmCtZM10Gu
2GgAnRGHpsPKz4bKLCXw9ylHnTFGdvfn
=EwiF
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message