-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 possib
On 02/02/2011 16:23, laredotornado wrote:
>
> You mean set timeouts at the database level?
Yes.
> What if the Tomcat thread is
> hung for some other reason?
Then you have an application bug to fix.
> Is there any setting that will cause Tomcat to
> kill a thread if that thread is "stuck"? - D
gt; -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
--
View this message in context:
http://old.nabble.com
On 02/02/2011 15:22, laredotornado wrote:
>
> Hi,
>
> We're using Tomcat 6.0.24. We would like Tomcat to kill stuck threads after
> a certain period of time, but Tomcat doesn't appear to be doing this.
> Specifically, when the database doesn't return results, the connections just
> build up. H
ything we might
need to add to get Tomcat to kill stuck connections? - Dave
--
View this message in context:
http://old.nabble.com/Trouble-with-connection-timeout-settings-tp30826944p30826944.html
Sent from the Tomcat - User mailing list archiv
