You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Bernd Eckenfels <ec...@zusammenkunft.net> on 2015/11/05 03:29:13 UTC

tomcat timeout handling

Hello,

in this bug https://bz.apache.org/bugzilla/show_bug.cgi?id=58565 there
was some dicussion on download timeouts.

I had noticed that tomcat does close slow/hanging downloads after the
connectTimeout=20s even when the documentation
(http://tomcat.apache.org/tomcat-8.0-doc/config/http.html) reads:

connectionTimeout	

The number of milliseconds this Connector will wait, after accepting a
connection, for the request URI line to be presented. Use a value of -1
to indicate no (i.e. infinite) timeout. The default value is 60000
(i.e. 60 seconds) but note that the standard server.xml that ships with
Tomcat sets this to 20000 (i.e. 20 seconds). Unless
disableUploadTimeout is set to false, this timeout will also be used
when reading the request body (if any).


I think this is wrong, it does not only apply to the initial line but
also the output. Maybe this could be clarified, especially in relation
with uploadTimeout and keepAliveTimeout. Especially when does the
connector transition from one to the other.

Greetings
Bernd


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


Re: tomcat timeout handling

Posted by Rémy Maucherat <re...@apache.org>.
2015-11-05 20:57 GMT+01:00 <ec...@zusammenkunft.net>:

> This is/was a bug report against the documentation which does not document
> the timeout correctly.
>
> Yes, ok, it could be improved :)

Rémy

Re: tomcat timeout handling

Posted by ec...@zusammenkunft.net.
This is/was a bug report against the documentation which does not document the timeout correctly.

-- 
http://bernd.eckenfels.net

-----Original Message-----
From: "Rémy Maucherat" <re...@apache.org>
To: Tomcat Developers List <de...@tomcat.apache.org>
Sent: Do., 05 Nov. 2015 10:09
Subject: Re: tomcat timeout handling

2015-11-05 3:29 GMT+01:00 Bernd Eckenfels <ec...@zusammenkunft.net>:

> I think this is wrong, it does not only apply to the initial line but
> also the output. Maybe this could be clarified, especially in relation
> with uploadTimeout and keepAliveTimeout. Especially when does the
> connector transition from one to the other.
>
> Obviously, the connection timeout is also used for output. Input is
specifically discussed since client's input is usually far slower and less
reliable, especially when dealing with large posts.

This was discussed at length in the relevant BZ, which you looked at. The
situation is now understood but there is no better solution than the
current behavior. In your situation, the most efficient is probably to
configure a smaller output buffer.

Note: I believe the message should be on the user list.

Rémy

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


Re: tomcat timeout handling

Posted by Rémy Maucherat <re...@apache.org>.
2015-11-05 3:29 GMT+01:00 Bernd Eckenfels <ec...@zusammenkunft.net>:

> I think this is wrong, it does not only apply to the initial line but
> also the output. Maybe this could be clarified, especially in relation
> with uploadTimeout and keepAliveTimeout. Especially when does the
> connector transition from one to the other.
>
> Obviously, the connection timeout is also used for output. Input is
specifically discussed since client's input is usually far slower and less
reliable, especially when dealing with large posts.

This was discussed at length in the relevant BZ, which you looked at. The
situation is now understood but there is no better solution than the
current behavior. In your situation, the most efficient is probably to
configure a smaller output buffer.

Note: I believe the message should be on the user list.

Rémy