Re: JIRA and CAS

domianx@gmx.de wrote:


Please do not top-post. Use trim-and-inline posting.

"cyber1boy" wrote:


I'm not familiar with the specific products, and absent the relevant code I
cannot tell precisely what caused the problem, but generally the message
refers to an attempt to create a session or otherwise modify the response
after the first part of the response has been sent back to the client.

Something is trying to re-open the output stream after it was already written to.

Is there a servlet filter involved that might be writing to the response
instead of merely forwarding to the next request processor?

Googling around for the error message (always a good thing to do in such
cases, BTW) indicates that this can happen if certain frameworks (Struts,
Spring) attempt to post an error message into the response after dealing with
another error that broke the request-handling flow, perhaps without cleanly
exiting the logic that got interrupted.

I see other messages relating to JIRA and this error in my search results.
However, they were in the minority - there were reports of this message from
the use of all kinds of frameworks.

The problem often happens when custome code makes a framework call that takes
the response object and writes to it under the hood, then itself tries to
'getSession()' or otherwise perform processing that has to happen strictly
within the request-processing phase. It also happens when one writes to the
response, then issues a RequestDispatcher forward() call.

GIYF.

--
Lew