[email protected], [EMAIL PROTECTED]
> Subject: Re: Threads running in cgi scripts...
>
> Kevin,
>
>Yes, that error correlates directly with a CGI timing out. (See
> http://httpd.apache.org/docs/2.0/mod/core.html#timeout for how that
> timeout is controlled.)
>
>
Kevin,
Yes, that error correlates directly with a CGI timing out. (See
http://httpd.apache.org/docs/2.0/mod/core.html#timeout for how that
timeout is controlled.)
If you still want to try to use persistant perl threads, you'll
probably need to use mod_perl2 with the PerlChildInitHandler dir
Eric,
Thanks for the help. One other things that might show some insight
into the problem, is that I seeem to get this error in the Apache log
when the thread finally dies. (70007) The timeout specified has
expired: ap_content_length_filter: apr_bucket_read() failed.
One other question -- if I
Kevin,
If you are using a CGI script to start a perl thread, then it is
highly likely apache is timing out (the CGI hosting) your thread.
(Apache threads should block on an executed CGI until it returns, or
apache times it out, whichever occurs first.)
First of all, AFAIK, fork() is not an
No, that is already zero. I tried changing it to 100, but it had no
effect.
[EMAIL PROTECTED] wrote:
> So, my server dies after some time of successful operation. Is this
> due to Apache limiting how long a process can run?
Possibly. 'MaxRequestsPerChild 0' in httpd.conf may help.
Wa
