https://bz.apache.org/bugzilla/show_bug.cgi?id=69982
--- Comment #4 from Phil Clay <[email protected]> --- I was able to reproduce this with more logs enabled (finally). Specifically, I enabled: org.apache.tomcat.util.net: TRACE org.apache.coyote.http11: TRACE _org.springframework.http.server.reactive.AbstractListenerReadPublisher: TRACE _org.springframework.http.server.reactive.AbstractListenerWriteProcessor: TRACE _org.springframework.http.server.reactive.AbstractListenerWriteFlushProcessor: TRACE _org.springframework.http.server.reactive: TRACE I've uploaded a log for Tomcat 11.0.18, showing a success case and a failure case https://github.com/philsttr/tomcat_11_delayed_response/blob/main/logs/tomcat11.0.18.log It doesn't reveal much, but please take a look. The main difference I see is that - in the success case, the server encounters a closed channel exception after writing the response. I assume this is because the client received the full response and closed the connection. - in the failure case, the server does not encounter the exception. I assume this is because the client is still waiting on the remaining portion of the response, and hasn't closed the connection I haven't found any logging I can enable that shows when flushes occur. Can you recommend any other logs to enable? -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
