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=44334>. 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=44334 ------- Additional Comments From [EMAIL PROTECTED] 2008-02-01 11:42 ------- Created an attachment (id=21458) --> (http://issues.apache.org/bugzilla/attachment.cgi?id=21458&action=view) tcpdump capture of bad ajp13 POST retries Attached is tcpdump capture with snaplen 1500 demonstrating bad mod_proxy_ajp POST retries. This is a deliberately pathological example where the client didn't send POST message body until 3 seconds after it sent POST headers. As you can see, tomcat ajp13 connector hangs up on the first request after 500ms (FIN, packet 6). At 3.5s the client completes the POST request, apache sends the message body to tomcat (packet 8), and tomcat replies with RST (packet 10). At that point apache has the complete POST and it retries the request. It reconnects and sends the message header (packet 15) and nothing else. 500ms later tomcat ajp13 connector hangs up on it. Repeat until maxattempts exhausted. A useful way to see this in wireshark is View -> Time Display Format -> Seconds Since previous Capture Packet -- 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]
