httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 46634] Requests sometimes take too long, wrong time taken reported in logs
Date Wed, 04 Feb 2009 10:14:13 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=46634





--- Comment #9 from mb <m-b@nurfuerspam.de>  2009-02-04 02:14:12 PST ---
Hmmm... That doesn't sound very feasible to me, 'cause it would require us
stopping httpd in exactly that moment when any of the hundred parallel requests
hangs for a second or two. However, neither do we know beforehand, when that
will happen nor do we know which request is affected until it is logged. Even
if we tracked it down with wireshark in parallel, it would not be possible to
analyze the data that fast and stop httpd.

Of course, if there is any way to achieve this, we'll try. Any help to
accomplish this task is appreciated.

Another option would be some investigation in the sources. The problem seems to
occur somewhere after the last byte of the previous response is sent, the next
pipelined request is accepted on the connection, but before the log is written
for the first response.


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

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


Mime
View raw message