Hi.
Are we not a bit on the wrong track here ?
I believe that the timeout which Pang J. is mentioning, may be the browser-side timeout,
which is fixed at the browser level at about 5 minutes or so.
When a browser sends a request to a server, and it does receive /some/ response within the
next +-5 minutes, then the browser will drop the connection to the server, and pop up a
message saying "sorry, the server appears not to respond.."
In other words, it is not a server timeout, it is a client timeout.
The only way to avoid this, is to insure that the server sends at least /some/ temporary
response to the client (*), regularly, so that this browser timeout does not occur.
Unfortunately, that is a bit more complicated to set up, than just some
parameter somewhere.
But there must be plenty of past discussions of this issue already on the www, and
solution guidelines.
(*) Something like a message "Please wait, we are still calculating.."
As long as the browser receives /some/ response regularly, it will not time out.
On 28.03.2018 05:11, Jie Gao wrote:
* PANG J. <pa...@uk2.net> wrote:
Date: Wed, 28 Mar 2018 10:49:46 +0800
From: "PANG J." <pa...@uk2.net>
To: modperl@perl.apache.org
Subject: Re: handler timeout
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101
Thunderbird/52.6.0
On 2018/3/28 ζζδΈ AM 10:41, Jie Gao wrote:
To start with, is your hosting machine running out of resources (CPU cycles,
memory, etc)?
No. resources are enough. we have about 100 servers for computing, each with
24 physical cores. But yes, the system load most time is high.
Your system load probably would explain it. Your tasks are computation
intensive, and unless your programmes are multi-threaded, they each will be
limited by the speed of the single CPU core it runs on.
And what is the timeout value you have configured for Apache? The defaults
might be too low.
Timeout 300
I'd increase this timeout value gradually to suit the need.
Regards,
Jie
