Skip to content
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

java.lang.IllegalStateException: getOutputStream() has already been called for this response [SPR-10293] #14927

Closed
spring-issuemaster opened this issue Feb 13, 2013 · 3 comments
Assignees
Milestone

Comments

@spring-issuemaster
Copy link
Collaborator

@spring-issuemaster spring-issuemaster commented Feb 13, 2013

jay opened SPR-10293 and commented

  1. run the roo script
  2. import maven project to STS
  3. add the project to Vmware vFabric tc server v2.7
  4. start the server
  5. open Home page

then got lots of getOutputStream() exception

Windows 64bit version - STS Version: 3.1.0.RELEASE Build Id: 201210061306


Affects: 3.1 GA

Attachments:

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

@spring-issuemaster spring-issuemaster commented Feb 15, 2013

Juergen Hoeller commented

This is usually caused by mixed getWriter() and getOutputStream() usage on an HttpServletResponse, i.e. by mixed textual and binary content generation on the same response. I've also seen this caused by a JSP trying to forward to a binary download controller - with a bit of comments/empty lines having been generated by the JSP before, and the response having been flushed already.

Anyway, jay, it would be good to see your stacktrace here. Could you post it?

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

@spring-issuemaster spring-issuemaster commented Feb 15, 2013

jay commented

Thanks, attached the stacktrace.

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

@spring-issuemaster spring-issuemaster commented Feb 27, 2013

Phil Webb commented

I have tried to replicate the issue with the latest STS release without success and I cannot see anything in the stacktrace that indicates an issue within the core framework. If you are still having issues I suggest raising a bug with the Spring Roo team who will be in a better position to track down the root cause. We can reopen this bug if it turns out not to be something specific to Roo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.