Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Message-ID: <451D46E4.4030306@apache.org>
Date: Fri, 29 Sep 2006 18:16:36 +0200
From: Mladen Turk <mturk@apache.org>
User-Agent: Mozilla
MIME-Version: 1.0
To: Tomcat Developers List <dev@tomcat.apache.org>
Subject: Re: Tomcat keepAliveTimeout
References: <451D393E.8030407@apache.org> <451D41FF.5010100@hanik.com>
In-Reply-To: <451D41FF.5010100@hanik.com>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit

Filip Hanik - Dev Lists wrote:
> you are correct, soTimeout should not, imho, change depending on the 
> thread count.
> if the user sets 20 seconds for soTimeout then it should stay that way.
>

Right. With the current code you can only deduct what the actual
timeout will be. Like said, for 40 sec timeout it can be
40, 20, 13 or 2.

> 
> I see how soTimeout would be different from keepAlivetimeout when the 
> servlet is invoking a blocking read on the servletinputstream.

Actually its very simple:
soTimeout: The time to read the data.
keepAliveTimeout: The time between two requests.

Those things has been elaborated long time ago.
I'm sad that my first patch to the Tomcat get reverted immediately
without any -1. Anyhow, I'll think twice before next commit.

Regards,
Mladen.

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