DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16363>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16363 Stack Overflow accessing compiled JSP - Tomcat 3.2.4 and JDK 1.4.1 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Unknown |Jasper ------- Additional Comments From [EMAIL PROTECTED] 2003-01-24 13:59 ------- We've been investigating this one a bit more, and have the following to add: 1. The problem seems to be triggered when the browser breaks a connection to an compiled-by-Tomcat page unexpectedly. The following lines invariably show up in the tc.log file (if I turn up logging): Ctx( /emx ): IOException in: R( /emx + SOME_JSP_FILE + null) Software caused connection abort: socket write error Ctx( /emx ): IllegalStateException in: R( /emx + SOME_JSP_FILE + null) Current state = FLUSHED, new state = CODING_END Ctx( /emx ): Error: exception inside exception servlet null class java.net.SocketException Ctx( /emx ): IllegalStateException in: R( /emx + SOME_JSP_FILE + null) Current state = FLUSHED, new state = CODING Ctx( /emx ): Error: exception inside exception servlet null class java.lang.IllegalStateException Ctx( /emx ): IllegalStateException in: R( /emx + SOME_JSP_FILE + null) Current state = FLUSHED, new state = CODING Ctx( /emx ): Error: exception inside exception servlet null class java.lang.IllegalStateException repeat ad naseaum and ad out-of-memoriam 2. Notice that I said that Tomcat had to compile the page. If we pre-compile the JSPs into servlets and create explicit servlet mappings, the problem goes away. This implies to me that this bug is in Jasper, so I've changed the "Component" for this bug report. 3. We've tried the following combinations. The first three lines indicate what version of the JDK the code in question was compiled under. "P" in the JSPs line indicates pre-compiled JSPs as I describe above; lack of "P" indicates Jasper-compiled JSPs. I've abbreviate for brevity - 1.3 is 1.3.1_04 and 1.4 is 1.4.1_01 Tomcat 3.2.4 1.3 1.3 1.4 1.3 1.4 1.3 1.4 1.3 JSPs 1.4 1.3P 1.4 1.3P 1.4 1.4 1.4P 1.4P Our Code 1.3 1.3 1.3 1.3 1.4 1.4 1.4 1.4 Runtime 1.4 1.3 1.4 1.4 1.4 1.4 1.4 1.4 Result FAIL OK FAIL OK FAIL FAIL ??? ??? We decided not to test the last two cases because they don't help us much - we need a combination that will let us run without pre-compiling the JSPs. However, if whoever picks up this bug feels it'll be helpful, we can run them fairly quickly. 4. No clue whether this happens in later versions of Tomcat. We were going to convert to 4.x but ran into problems (not me, so I don't know the details) and we dropped it. Now that this is happening, we're going to try to tackle it again to see what happens. I'll update this bug when we know. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
