On 25/11/2014 01:33, Massimo Manghi wrote:
On 11/24/2014 06:58 PM, Georgios Petasis wrote:
Well it is a badly designed system. I have a lengthy calculation (like 8
yes, definitely
hours). So the caller (which is an apache tomcat, written in java) calls
my service (apache2 + rivet), and waits until I have finished. But for
some reason (I don't know), apache starts a second instance after about
2 hours, so I end up running multiple instances of the computation in
parallel.
I don't think it is an issue of connection timeout (both processes run
on the same server). Something internally in apache 2 times out, and
thinks the process serving the request has stopped, and tries to run
again the same request on another child.
TCP connections through loopback intefaces have timeouts like any other
TCP connections, don't they? The sharp 2 hours limit seems to be more
like something like a resource consumption limit imposed by the Apache
framework, maybe a CPU time consumed by the child process. From what you
say the data consumer (client) is not an ordinary web browser, so the
client itself could follow any policy and maybe restart the computation
when the server fails and drops the connection....just guessing....
I am guessing also. For sure, they don't have such a problem with
tomcat, where connections do not time out after 12 or more hours. It is
happening only under apache...
Best,
George
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org
For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
