Hi Mark,
I applied your advice. I added a directive to my error page, so it wont
create a session variable, and therefore won't try to create a session if it
does exist (%@ page session=false%).
Well, IT WORKED! I got rid of the java.lang.IllegalStateException: Cannot
create a session after the
Brian wrote:
...
In fact, I have had LOTs of problems with beans that dissappear
that's usually a problem associated with age. I was going to ask, but
I have been dealing with these randomic problem for YEARS,
you've answered that yourself.
;-)
On 23/09/2010 07:42, Brian wrote:
What does response has been commited mean? I have a theory: Maybe it means
that in the java code that the container generated for my JSP, at least one
out.write() method has already been used, which means that It already has
started to send html code to the
Wow. This is what I call Premium Support! I was thinking about writing en
email to you, Mark, since I was studying the Tomcat source code and saw your
name there. But thought it would be too direct to write to you. I'm honored
to receive your response, really :-)
Thanks for the commited
On 23/09/2010 12:01, Brian wrote:
Thanks for the commited explanation, but I still have a doubt: Where in my
code do I commit? I don't do it explicitly, so it is happening at some point
automatically but I don't know exactly where/when. If a full buffer is not
the cause, what is it for the
Rather than chasing it at the view end why don't you just call getSession in
the controller or a filter? Then you have no need of doing anything with any
buffers etc.
As to what exception is happening it's the illegal state. Whatever has happened
up to that point of the processing has flushed
On 23/09/2010 12:01, Brian wrote:
Thanks for the commited explanation, but I still have a doubt: Where
in my code do I commit? I don't do it explicitly, so it is happening
at some point automatically but I don't know exactly where/when. If a
full buffer is not the cause, what is it for
