Bug ID: 63662
           Summary: Tomcat tries to process ClientAbortExceptions
           Product: Tomcat 8
           Version: 8.5.43
          Hardware: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Connectors
  Target Milestone: ----

We have recently upgraded Tomcat from 8.5.32 to 8.5.43, and we started
receiving ClientAbortExceptions, even though we are explicitly catching them.
On 8.5.43, if there is an ClientAbortException, Tomcat tries to service it like
a regular server exception: it tries to generate the error 500 page.

I've debugged this and Tomcat 8.5.43 chooses a different path in
org.apache.catalina.core.StandardHostValve#invoke(Request, Response) than
8.5.32. This:

// Look for (and render if found) an application level error page
if (response.isErrorReportRequired()) {

returns true on 8.5.43, but false on 8.5.32.

I suspect, this has changed after "response.setError();" was added to
org.apache.coyote.AbstractProcessor#setErrorState(ErrorState, Throwable).

Expected behavior: Tomcat ignores ClientAbortExceptions. It doesn't make sense
to anything else with the response, after we already have lost the client.

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to