On 22/03/2012 11:40, André Warnier wrote: > Martin Gainty wrote: >> Mitch >> One possible cause >> >> FE Application creates session >> passes queryString or posted Data (hopefully in Sesion) to backend >> Axis WebService >> Objects are serialized to disk with existing JSESSIONID >> FE times out >> back end responds to a disconnected session and tries to re-create >> session with old JSESSIONID >> Illegal StateException is thrown when client tries to (re)create new >> session with old serialized JSESSIONID >> > +1 > I would add that the "illegal state" indicated by the error message is a > special tomcat quantum state, resulting from a situation in which the > response, while not being totally sent yet, is in fact partially sent > already, causing a certain amount of probabilistic confusion a the level > of the event horizon. > This is caught by a hidden class in Tomcat, invoking a singleton object > which writes a generally nonsensical message in one of the logs, chosen > at random. > Due to the nature of the error, it is of course extremely hard to > reproduce, as one can find out either the exact time of the event, or > its location, but not both.
And for those of your reading the archives not familiar with some of our better known characters, Martin - as usual - is talking complete and utter nonsense and André - if it wasn't obvious - is taking the mickey. If you need the real answer, take a look at Konstantin's earlier reply. If you want a good laugh, then this thread certainly has some potential. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
