Tomcat question

[Andrey Orekhov]

Whilst running my web application on Tomcat I often get such error message (on server console). And when it is started it is repeating many times (100-1000).
2002-01-16 01:34:08 - Ctx( /mpv2g ): IllegalStateException in: R( /mpv2g + /login.jsp + null) Current state = FLUSHED, new state
= CODING
What is it and how to prevent it?

[Tony Alicea]

I am moving this question to the Apache/Tomcat Forum...

[Andy Cochrane]

Hi Andrey,
I am having exactly the same problem, did you ever figure out how to fix this?
Andy

Originally posted by Andrey Orekhov:
Whilst running my web application on Tomcat I often get such error message (on server console). And when it is started it is repeating many times (100-1000).
2002-01-16 01:34:08 - Ctx( /mpv2g ): IllegalStateException in: R( /mpv2g + /login.jsp + null) Current state = FLUSHED, new state
= CODING
What is it and how to prevent it?

[alex reznik]

Andrey,
ne dreif'
Alex

[Tim Holloway]

I don't know of any issues specific to Tomcat. That's the kind of message you'd expect to see if you are trying to do two incompatible things at once. For example, if you do a schedule a forward request and then attempt to output from the current servlet/jsp.

[Annekee Dufour]

I am experiencing the same problem (tomcat 4.1, jdk 1.4):
endless lines like this:
2003-10-31 13:00:05 - Ctx( /suwinet-inkijk ): IllegalStateException in: R( /suwinet-inkijk + /rh + /bkwi/info/info) Current state = FLUSHED, new state = CODING
2003-10-31 13:00:05 - Ctx( /suwinet-inkijk ): IllegalStateException in: R( /suwinet-inkijk + /rh + /bkwi/info/info) Current state = FLUSHED, new state = CODING
2003-10-31 13:00:05 - Ctx( /suwinet-inkijk ): IllegalStateException in: R( /suwinet-inkijk + /rh + /uwv/cwi/overzicht) Current state = FLUSHED, new state = CODING
followed by:
2003-10-31 13:00:23 - Ctx( /suwinet-inkijk ): Exception in: R( /suwinet-inkijk + /rh + /bkwi/info/info) - java.lang.StackOverflowError
at java.util.Hashtable.get(Hashtable.java:329)
at java.util.Properties.getProperty(Properties.java:480)
at java.lang.System.getProperty(System.java:574)
at sun.security.action.GetPropertyAction.run(GetPropertyAction.java:66)
at java.security.AccessController.doPrivileged(Native Method)
at java.io.PrintWriter.<init>(PrintWriter.java:72)
at java.io.PrintWriter.<init>(PrintWriter.java:57)
at org.apache.tomcat.context.ExceptionHandler.doService(DefaultCMSetter.java:276)
at org.apache.tomcat.core.Handler.service(Handler.java:287)
at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
at org.apache.tomcat.core.ContextManager.handleError(ContextManager.java:1183)
at org.apache.tomcat.core.Handler.service(Handler.java:312)
at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
at org.apache.tomcat.core.ContextManager.handleError(ContextManager.java:1183)
(the beginning of the stacktrace varies, the last three lines repeat ad nauseam)
Our application uses only one servlet, no forwards, no includes, no resetting or flushing of the outputbuffer. Any hints?

[Mike Curwen]

this is a rare error that crops up every so often...

Here's a possible solution...

http://marc.theaimsgroup.com/?l=tomcat-user&m=103763489114072&w=2

Short version: Can you upgrade to jdk 1.4.2 or downgrade to jdk 1.3.x ?

[Annekee Dufour]

The jdk upgrade didn't help, hacking the tomcat code did. Look here: <a href=" http://issues.apache.org/bugzilla/show_bug.cgi?id=19002"> http://issues.apache.org/bugzilla/show_bug.cgi?id=19002<a>.