https://bz.apache.org/bugzilla/show_bug.cgi?id=60718
--- Comment #2 from Brett Kail <bjk...@gmail.com> --- Created attachment 34742 --> https://bz.apache.org/bugzilla/attachment.cgi?id=34742&action=edit test project I reviewed bug 60385 before opening this bug, and I do not think it is relevant. That bug is about requestInitialized throwing an exception and therefore requestDestroyed not being called, which is reasonable. This bug throws no exception from requestInitialized, but it forces a client error during getOutputStream().write(). I am attaching a test project that demonstrates the problem for me (on Windows at least, but earlier version of the test also failed on Linux). Install the WAR in Tomcat, then run the main method in TestServlet. The main method connects to four endpoints, so I would expect four "+ requestDestroyed" messages. On Tomcat 8.5.6, there are only three (missing async=sync). On 8.5.11, there is only one (missing all async scenarios). Additionally, 8.5.11 has a noisy setErrorState stack trace (seems unnecessary?) and an IllegalStateException from AsyncStateMachine.asyncError. -- 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
