Summary

• When using @ExceptionHandler (or @ControllerAdvice), exceptions thrown while writing to a StreamingResponseBody are not handled correctly (or at least as I expect them to be…) when the request mapping returns ResponseEntity<StreamingResponseBody>
• Exception handling does work as expected when the return type is just StreamingResponseBody
• It’s possible my understanding of how these should work is incorrect, however I haven’t seen any evidence yet to point to this

Description

• If a runtime exception occurs while writing to the StreamingResponseBody wrapped in a ResponseEntity the endpoint does invoke the @ExceptionHandler but returns a 500 status with no response body no matter what
• If the request mapping returns a StreamingResponseBody directly, error handling does work as expected, and the response code and response body are correct
• While writing tests for this, I can’t get the tests to return anything other than 200 status. While running tests, I also don’t see the exception handlers getting invoked. I’m not sure if this is another bug or if my test setup is incorrect. If you hit the endpoints directly in the browser or via CURL, you do see the 500 status with no body. This is my first time using StreamingResponseBody so I apologize if I’m just doing things incorrectly
• Sample project to reproduce: https://github.com/austinarbor/spring-boot-streaming-response-issue

Misc

• Spring Boot: 2.3.1 / 2.3.2
• Spring Framework: 5.2.8
• Java Version: 11
• StackOverflow Question