-
Notifications
You must be signed in to change notification settings - Fork 41.1k
Since upgrade to 2.0.1: IllegalStateException: InputStream has already been read #12939
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
Comments
Markdown ate |
I think you can turn this into something very useful by extracting that controller in a sample app we can run ourselves and open an issue in the Spring Framework issue tracker. This discussion shouldn't really happen here given the stacktrace you've shared. |
Here's the thing:
That sample app will not be of much a help, as it probably won't reproduce the issue. I't really nothing too exoctically. It's a Controller returing just said |
Looking at what the controller does and the stacktrace might help the Spring Framework team to figure out what might cause this in Spring Framework 5 and not in Spring Framework 4. |
True, I'll do that. I just hoped to avoid the hassle around submitting to your Jira. |
For reference: https://jira.spring.io/browse/SPR-16754 |
I upgraded a web application from Spring-boot-1.5.10 to 2.0.1. Since then I notice these frequent errors:
The particular controller returns a ResponseEntity to download an InputStream. Also it seems only a fraction fails. Many download succeed. I know this report is not very helpful, but unfortunately I also don't know where to look further to get more details. Maybe this InputStreamResource sounds familiar to someone and can point me to a recent change with Spring-5.
The text was updated successfully, but these errors were encountered: