Default async timeout handling results in Logged Exception for Tomcat 8.5.x [SPR-14739] #19305
When the response has been already committed and the request timeouts afterwards there is an AsyncRequestTimeoutException logged on Tomcat 8.5.x.
I guess this is due to the change in #19233.
Affects: 4.2.8, 4.3.3
Referenced from: commits spring-projects/spring-framework-issues@d44d40c
Backported to: 4.2.9
The text was updated successfully, but these errors were encountered:
Rossen Stoyanchev commented
Okay thanks for that. So in an SSE scenario where at least one event has been sent, followed by a timeout.
A log message at that point isn't so out of place since the request timed out and the timeout wasn't handled (e.g. through a listener) and we can no longer change the response status to notify the client. However we can reduce the noise and handle the AsyncTimeoutException by logging a minimal debug message if the response is already committed.