On 03/05/2012 11:52, hunters1094 wrote:
> hi
>
> I have this problem too. I tried to find the solution, tried to use this
>
> http://stackoverflow.com/questions/8072311/illegalstateexception-cannot-create-a-session-after-the-response-has-been-commi
>
> Solution state-saving-method
>
> But it only reduces error times, but not removes completely.
>
> Thanks.
As Chuck says earlier - this is, in almost all cases, a side-effect of
the application or framework incorrectly persisting a
request/response/session object in a Servlet instance field or some
other location that is not thread safe.
p
--
[key:62590808]