Hello Nicolas, NC> Several possibilities :
NC> a) it's an infinite loop, it should then take a lot of CPU : it's a bug NC> and should be avoided. NC> b) Apache blocks sometimes while sending the answer to the client. NC> (status W = it seems to be the case here). You have to define the NC> Timeout var in httpd.conf to have it close the connection. It actually looks like the first option - it does eat a lot of CPU, and I have Timeout 120 in my httpd.conf. So I of course need to go & debug the problem, the question is then whether there is a way to limit a request processing time somehow so Apache would force a handler to terminate even if it is inside an infinite loop? -- Best regards, Michael mailto:[EMAIL PROTECTED] -- Neko : One VM to run them all (http://nekovm.org)
