https://bz.apache.org/bugzilla/show_bug.cgi?id=69982
--- Comment #8 from Phil Clay <[email protected]> --- You're not going to believe this. We worked together on a slightly different variant of this bug in 2022... https://bz.apache.org/bugzilla/show_bug.cgi?id=66076 And I believe the fix is almost exactly the same, just for a slightly different code path. I have a proposed fix here https://github.com/apache/tomcat/compare/main...philsttr:tomcat:bz69982_fix_async_response_write The above change fixes Tomcat 11 in my testing. Take a look. One potential improvement is removing the socketOrNetworkBufferHasDataLeft() method, and changing callers to call hasDataToWrite() instead. The only difference is that super.hasDataToWrite() also checks !nonBlockingWriteBuffer.isEmpty(); -- 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]
