Well, I sometimes get this error with my error page, which only gets called by Tomcat. This is what's in web.xml.
<error-page> <exception-type>java.lang.Exception</exception-type> <location>/error/er500.jsp</location> </error-page> If the stream has already been closed, I think then this is a Tomcat error. I am not sure how I could fix this. -----Original Message----- From: Ralph Einfeldt [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 24, 2002 4:35 AM To: Tomcat Users List Subject: AW: Error : Why IllegalStateException ? That's not a problem of web.xml. What make you think it is? (That kind of problem wouldn't be resolved by a restart) The typical reason for an IllegalStateException is that you (or any component that you use) try to write something to a response or a stream that already has bean closed (flushed). > -----Ursprüngliche Nachricht----- > Von: jose saloio [mailto:[EMAIL PROTECTED]] > Gesendet: Mittwoch, 24. Juli 2002 10:21 > An: [EMAIL PROTECTED] > Betreff: Error : Why IllegalStateException ? > > I have this error: > Current state = FLUSHED, new state = CODING > 7-10 11:09:48 - Ctx( /test): IllegalStateException in: R( > /test+) Current > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>