https://bz.apache.org/bugzilla/show_bug.cgi?id=58565
--- Comment #3 from Remy Maucherat <r...@apache.org> --- After debugging, it looks like it's a combination of factors. What happens is that the network stack buffers things a lot without blocking. At some point it will block until everything gets flushed. Unfortunately, the flushing takes forever due to the client speed limit, and a legitimate write connection timeout occurs in Tomcat. Then the network stack will continue trickling bytes to the client until the connection is closed due to the error (which occurred a long time before). I would recommend to *not* increase the timeout for the connection [that would be a workaround], and I doubt this can be fixed effectively. So this could end up as a WONTFIX. -- 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
