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=35160>. 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=35160 ------- Additional Comments From [EMAIL PROTECTED] 2006-12-15 07:36 ------- (In reply to comment #8) I was successful in reliably reproducing the problem using the previously posted configuration. What I do is applying some load on the server: /u01/opt/apache2/bin/ab -C ADPEHCRELEASE=000001 -c 10 -n 100000 http://server/index.html Then I also use curl to send requests in a loop: $ while [ 1 ] ; do curl -H "Pragma:" --header "Cookie: ADPEHCRELEASE=000001" --dump-header /tmp/hdr2 http://server/index.html ; done HI!! curl: (52) Empty reply from server HI!! HI!! HI!! HI!! curl: (52) Empty reply from server curl: (52) Empty reply from server HI!! HI!! Every time I get "Empty reply from server", there is a coredump and Apache forks a new process. The response from the URL requested is small enough to be elegible for in-memory caching. Just running ab does not seem to cause any coredumps. The problem starts to occur when I launch curl-loop. Apache is running on a dual-processor USparc-IIIi, solaris 8. IT is using MPM worker with the following settings: ServerLimit 6 ThreadLimit 100 StartServers 2 MaxClients 600 MinSpareThreads 10 MaxSpareThreads 200 ThreadsPerChild 100 MaxRequestsPerChild 0 -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
