Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4728E793.3070803@dueppe.com>
Date: Wed, 31 Oct 2007 21:37:39 +0100
From: =?ISO-8859-15?Q?Ingo_D=FCppe?= <mailing-lists@dueppe.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Unrecoverable error 200, request failed
References: <4724673D.6010301@dueppe.com> <47247F31.3030105@kippdata.de>
 <47248851.6020308@dueppe.com> <4724960F.5040103@kippdata.de>
In-Reply-To: <4724960F.5040103@kippdata.de>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit

Hi Rainer,
now I got it what you mean about the steady state.
Thx Ingo

Rainer Jung schrieb:
> Hi Ingo,
>
> Ingo D�ppe wrote:
>> Am I'm right, that with the following setting a reply_timeout is 
>> detected when the tomcat doesn't reply within 10 seconds and it will 
>> be set into error if more than 15 timeouts in a minutes are detected?
>>
>> worker.plexus.reply_timeout=10000
>
> Yes. The timeout gets reset every time mod_jk waits for the next 
> package. So it's not an overall response time timeout, but it limits 
> the longest pause allowed between reposnse packets. Usually it will 
> fire, between the point in time the request was forwarded to Tomcat 
> and the first request packet arrives. Most apps don't have huge delays 
> after that point.
>
> See also
>
> http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html
>
> for a description of all possible timeouts.
>
>> worker.plexus.max_reply_timeouts=30
>
> In case you assume a steady rate of long running requests, yes: 15 per 
> minute. In case there were no long running requests for a long time, 
> our intrnal counter will be zero and we will allo up to 30 long 
> running requests before triggering the error status.
>
> The counter gets divided by 2 every minute, so that older events count 
> less the longer they are away. A worker that worked fast for a long 
> time can use all of the 30 events, if it already had 30 (or 29) 
> timeouts in the minute before, only 15 are free the next minute.
>
> Regards,
>
> Rainer
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>


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