DO NOT REPLY [Bug 42473] - Apache2 problem with MaxClient and/or TimeOut

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42473>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42473


rpluem@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO




------- Additional Comments From rpluem@apache.org  2007-05-21 14:14 -------
This might be a problem with PHP / Squirrelmail. Please try to obtain backtraces
from "hanging" processes (see http://httpd.apache.org/dev/debugging.html).
You might misread the meaning of Timeout in httpd. Timeout here means the
maximum amount of time httpd waits to *write* data to or to *read* data from the
network. If you are using PHP via mod_php (running as a CGI is a different
story) and your php script simply generates no output httpd will keep the
connection open forever which works as designed as there is nothing to read from
the network for httpd (we are sending the response) and there is nothing to
write to the network (since the script produces no output). The
max_execution_time setting in PHP is used to prevent such long running scripts.
I cannot tell you if this works reliable.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org