DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14604>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14604 Log file piped to a process causes threads to lock Summary: Log file piped to a process causes threads to lock Product: Apache httpd-2.0 Version: 2.0.43 Platform: Sun URL: http://www.california.com/ OS/Version: Solaris Status: NEW Severity: Minor Priority: Other Component: Core AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] Compiled Apache using Prefork, Worker and threadpool to test this on various implementations of the thread schemes, and all three had the same problem. Writing to the log file becomes blocking somewhere in the code, and all the processes were sleeping on the Write command to the log file descriptor if the web server was hit with heavy load. Apache 1.3.7 seems to work fine with this scheme, though notably, has the other piped logfile issue. (Search for "Pipe Log") I'm still investigating whether this was the logging process that was blocking, but considering the program works fine with apache 1.3.7, I think this maybe a threading issue. Reguardless, if the process is actually stopping input, Apache should start discarding log file lines after a preset amount of time anyway to prevent degredation of the server. The fix of course? Use flat log files instead of logging to a process. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
