Michael Pliskin a écrit :
Hello list,
does anybody know if there is a way to limit the time a neko http
handler can handle request? I have Apache + mod_neko running on
production, and sometimes I see the following in server status:
17-0 23678 0/1319/1319 W 27.84 56562 0 0.0 0.98
0.98 217.66.145.207 go.comapping.com POST /cgi-bin/comapping.n
HTTP/1.1
if you read that, it says that the current request is being
processed for 56562 seconds (15 hours!) by now. I am looking for the
ways to debug that, but the first thing to do for me is to prevent
such long processing at all as it hurts the server quite a bit. Any
pointers?
Several possibilities :
a) it's an infinite loop, it should then take a lot of CPU : it's a bug
and should be avoided.
b) Apache blocks sometimes while sending the answer to the client.
(status W = it seems to be the case here). You have to define the
Timeout var in httpd.conf to have it close the connection.
Best,
Nicolas
--
Neko : One VM to run them all
(http://nekovm.org)
