-
Notifications
You must be signed in to change notification settings - Fork 37.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AsyncRequestNotUsableException thrown and logged after upgrade from Spring Boot 3.2.3 to Spring Boot 3.2.4 #32509
Comments
The change in behavior is due to #32340. We'll transfer this to Spring Framework so that they can investigate further. |
What's actually logging the exception? Previously, this would have been |
Hi looks like this is traced in a custom exception handler annotated with @ControllerAdvice. What is the recommendation here? I could simply ignore this specific exception, but what would be the performance impact of exceptions being generated/thrown on every request? Best regards |
In this case the exception only wraps the The exception implies the response is no longer usable, and you can't send any more data. You can treat it in the same way that you would the underlying I'm closing as there is nothing for us to do, but feel free to comment if necessary. |
How did you solve it?I am facing the same problem. Thanks. |
We are also seeing this error after an upgrade, it doesn't seem to happen for every request, just those that have used |
We didn't . The only solution I see is to suppress the exception in the custom exception handler. |
From what I see what has changed is the exception type thrown. Before spring-web:6.1.5 a ClientAbortException was thrown. Since 6.1.5 a AsyncRequestNotUsableException. So adding AsyncRequestNotUsableException to the exception handler will restore the old state. |
Hi
after upgrading to spring boot 3.2.4 from 3.2.3 our applications start logging this exception over and over (I suspect on every request):
this did not happen with the 3.2.3 version and after a rollback the exceptions are no longer logged.
The exceptions themselves do not seem to have any functional impact.
Used JVM: Amazon Corretto JDK 21.0.2
Best regards
Vasil
The text was updated successfully, but these errors were encountered: