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=36636>. 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=36636 ------- Additional Comments From [EMAIL PROTECTED] 2005-09-15 12:11 ------- Thanks for the remark on SIGPIPE (I know, I should have rtfm :) Anyway, when I block outgoing RST packets from my test machine so I can send my packet dump replay without interference from the host TCP/IP stack (since it uses a libndis userspace stack for replaying), the host stack does not reply with a RST to attempts from the server that is trying to push the data to the client [of the aborted replayed PROPFIND request]. That lead to the ability to reproduce the problem in all cases. Since your patch to mod_dav (check for aborted) and my analogous patch for core_output_filter reduce the number of writes to one, while the readonly DavLockDB patch further reduces the "problem" to serialized write-access, the remaining poll() call most likely conforms to the protocol. We are reducing the timeout and looking into the proposed alternative backends for mod_dav. Thank you very much for your help in pinning down the problem! What are the chances these patches (or similar, improved ones) make it into mainstream Apache? -- 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]
