Just one thing to confirm... I'm assuming Pound's TimeOut just measures latency before the server starts returning it's response. Once the response starts streaming, I'd assume it can't timeout anymore. Does this sound right to everyone?
I also saw there was a Client Timeout, and have started playing with this. I read the description in the man page (below), but still don't understand how this condition could happen. HTTP is a stateless protocol. Is this referring to if the client takes a long time to transmit the request data, or ACK back after the request is received?
Except from Man Page
Client value - Specify for how long Pound will wait for a client request (default: 10 seconds). After this long has passed without the client sending any data Pound will close the connection. Set it higher if your clients time-out on a slow network or over-loaded server, lower if you start getting DOS attacks or run into problems with IE clients. This value can be overridden for specific listeners.
Thanks for the help,
Pete
On Dec 15, 2007, at 3:43 PM, Pete DeLaurentis wrote:
PROBLEM: For some longer requests that take around 5 seconds to execute an "Internal Server Error" is returned. There are plenty of 5 or 6 or 7 second requests that go through okay.
TIMEOUTS: My timeout is the default for Pound (I have not specified a value, and received an error when I tried). But I don' think this is a timeout problem: if it was the problem would be repeatable based on how long the request took to execute. This is influenced by it, but it seems there are other factors.
For the sake of curiosity, what happens if you increase the timeout to say, 45 seconds? It sure sounds like a timeout problem...
Thanks David.
I just set the timeout to 45 seconds, but the problem persists. There doesn't seem to be a hard cut-off since some long requests work. Any other ideas?
-Pete
--
To unsubscribe send an email with subject unsubscribe to
pound@apsis.ch.