https://bz.apache.org/bugzilla/show_bug.cgi?id=65137
--- Comment #4 from Mark Thomas <ma...@apache.org> --- The connection is going to get closed due to the write timeout regardless. The best we can do here is avoid the additional corruption at the end of the truncated response. Tomcat is at the mercy of the JVM and the OS here. If the OS/JVM takes longer than a write timeout to allow Tomcat to write a chunk of the output (typically 8k) then the timeout is going to happen. You might also want to experiment with setting socket.txBufSizebut do not the warnings in the docs about using too small a value. Fixed in 10.0.x for 10.0.3 onwards where NIO and APR/Native were impacted. Back-ports for 9.0.x and 8.5.x to follow. -- 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
