tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: Trouble with connection timeout settings
Date Wed, 02 Feb 2011 23:38:01 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

laredotornado,

On 2/2/2011 11:23 AM, laredotornado wrote:
> You mean set timeouts at the database level?

I would do it at the query level. The JDBC API has overloaded methods
for Statement.executeQuery and friends that all take timeouts.

It's possible that your database allows you to set a global (or session)
timeout for all queries, but that's beyond the scope of anything Tomcat
could provide for you.

> Is there any setting that will cause Tomcat to kill a thread if that 
> thread is "stuck"?

Tomcat can't tell the difference between a thread that is doing
something useful or something not useful: only you can tell the difference.

You are welcome to write some kind of sweeper thread that examines each
thread at an interval and makes some objective (or subjective, I guess)
decision about the state of the thread and call any number of methods on
it including interrupt(), etc.

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

iEYEARECAAYFAk1J6tkACgkQ9CaO5/Lv0PBzWQCgwsfm2besCJMPYs5x3gS3sKHN
hgYAoJrYh5Dz5o+X8Dam+BEDpg9rTQja
=iqvn
-----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