Henrik-
Im would recoomend acquiring a HTTP sniffer such as Packetyzer
http://www.networkchemistry.com/products/packetyzer.php
to see ascertain HTTP packet characteristic timing deltas and to
ulltimately determine who/what is timing out the connection
The aforementioned suggestions on httpd.conf attributes I provided are ways
for Apache Server to accomodate the slow connections
Determining what is causing the connections to degrade and eventually time
out and why the connection is degrading would be the best way to approach
the situation-
Good Luck,
Martin-
----- Original Message -----
From: "hv @ Fashion Content" <[EMAIL PROTECTED]>
To: <users@tomcat.apache.org>
Sent: Friday, December 02, 2005 12:37 PM
Subject: Re: When does 408 happen ?
Thank you for your response.
The odd thing is that I am dealing with pages generated by Tapestry that
normally take around 5ms and in the worst cases I have seen 300ms. My
manual response time shouldn't be an issue as the browser doesn't have a
JSESSION cookie currently, so a new session will be created at some point.
I basicly have a classic form based login form, and when I submit the form
I get a 408 status.
Are you saying that 408 is caused by the POST submit being broken into
multiple packets and the time between them are beyond a certain httpd
threshold; And that is the only situation where a 408 is returned.
As I understand it what you are referring to is internal http protocol
handling in httpd. Since the error message is created by Tomcat, I would
expect it to reflect Tomcat http protocol handling.
Henrik
"Martin Gainty" <[EMAIL PROTECTED]> skrev i en meddelelse
news:[EMAIL PROTECTED]
look at these parameters in httpd.conf
http://httpd.apache.org/docs/1.3/mod/core.html#keepalive
specifically
#The TimeOut directive currently defines the amount of time Apache will
wait for three things:
#~The total amount of time it takes to receive a GET request.
#~The amount of time between receipt of TCP packets on a POST or PUT
request.
#~The amount of time between ACKs on transmissions of TCP packets in
responses.
#you may want to increase this value to
Timeout 300
#KeepAlive implies that dynamic content such as CGI output, SSI pages,
and server-generated directory listings will generally NOT #use KeepAlive
connections to HTTP/1.0 clients since the length must be known before
transmission
KeepAlive On
#The MaxKeepAliveRequests directive limits the number of requests allowed
per connection when KeepAlive is on. If it is set to "0", #unlimited
requests will be allowed. We recommend that this setting be kept to a
high value for maximum server performance. In
#Apache 1.1, this is controlled through an option to the KeepAlive
directive.
#I would advise setting this to 0
MaxKeepAliveRequests 0
#The number of seconds Apache will wait for a subsequent request before
closing the connection. Once a request has been received, #the timeout
value specified by the Timeout directive applies.
#Setting KeepAliveTimeout to a high value may cause performance problems
in heavily loaded servers. The higher the timeout, the #more server
processes will be kept occupied waiting on connections with idle clients.
#If your process load is high set this parameter lower
#If your process load is low set this parameter higher
KeepAliveTimeout 15
Viel Gluck,
Martin-
----- Original Message -----
From: "hv @ Fashion Content" <[EMAIL PROTECTED]>
To: <users@tomcat.apache.org>
Sent: Friday, December 02, 2005 7:39 AM
Subject: When does 408 happen ?
I get:
HTTP Status 408 - The time allowed for the login process has been
exceeded. If you wish to continue you must either click back twice and
re-click the link you requested or close and re-open your browser
Will it happen when a JSESSION cookie is on the client, but no longer on
the server?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
