https://issues.apache.org/bugzilla/show_bug.cgi?id=42996
--- Comment #39 from Mark Thomas <ma...@apache.org> 2009-08-16 22:03:13 BST --- Whlist Filip has been looking at Jerome's test case, I have been looking at Holger's and I am seeing similar results. I can only reproduce the error when using 127.0.0.1. This means the data isn't visible to Wireshark. When I use any of the normal Wireshark on Windows tricks to view the data, I can no longer reproduce the problem. I was able, with NT Kernel's Local Network Monitor, to view the traffic on 127.0.0.1. I saw the same thing Filip saw. When the error occurs, the client doesn't send any data. This is looking increasing like a client issue rather than a Tomcat one. Without a test case that shows Tomcat ignoring data that was sent or otherwise doing something as the TCP level that it should not that causes the client not to send the data, this issue is likely to get closed as INVALID. -- 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: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
