You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/06/20 10:54:49 UTC

DO NOT REPLY [Bug 10047] New: - IllegalStateException and Browser "back" button

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=10047>.
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=10047

IllegalStateException and Browser "back" button

           Summary: IllegalStateException and Browser "back" button
           Product: Tomcat 3
           Version: 3.2.3 Final
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Unknown
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: js@cataloom.com
                CC: js@cataloom.com


Hi,

I'm using JBOSS (2.4.4), Tomcat (3.2.3) and Struts (1.0.2) for my
web applications. I have a problem with endless IllegalStateException's
when I interrupt a Struts action with the browser back button. To be
sure that I haven't done anything wrong with redirects, error pages and
already commited buffers I've set up a simple test case:

- a "start" JSP with a link to a Struts action
- a Struts action, that writes a line to the logfile, waits some seconds
  and then forwards to the "success" page
- a simple "success" JSP


To reproduce the IllegalStateException's I first go to the start JSP page,
click on the action link and while the browser and the Struts action are 
waiting I hit the browser's back button. The result is that I'm on the 
preceding page again and the log gets filled with endless exception messages
(the logfile from JBOSS in this case):

INFO  Default: JBoss-2.4.4 Started in 0m:23s.505
INFO  Default: IllegalAction entered... <-- my action
INFO  Default: IllegalAction continue...
DEBUG EmbeddedTomcatServiceSX: 2002-06-19 12:00:47 - Ctx( /demo ): IOException
in: R( /demo + /illegal1.jsp + null) Socket closed
DEBUG EmbeddedTomcatServiceSX: 2002-06-19 12:00:47 - Ctx( /demo ):
IllegalStateException in: R( /demo + /illegal1.jsp + null) Current state =
FLUSHED, new state = CODING_END
DEBUG EmbeddedTomcatServiceSX: 2002-06-19 12:00:47 - Ctx( /demo ):
IllegalStateException in: R( /demo + /illegal1.jsp + null) Current state =
FLUSHED, new state = CODING
DEBUG EmbeddedTomcatServiceSX: 2002-06-19 12:00:47 - Ctx( /demo ):
IllegalStateException in: R( /demo + /illegal1.jsp + null) Current state =
FLUSHED, new state = CODING
... ad infinitum ...


The same happens when I deploy the example in a standalone Tomcat:

IllegalAction entered... <-- my action again
IllegalAction continue...
2002-06-20 09:34:31 - Ctx( /struts-test ): IOException in: R( /struts-test +
/illegal1.jsp + null) Socket closed
2002-06-20 09:34:31 - Ctx( /struts-test ): IllegalStateException in: R(
/struts-test + /illegal1.jsp + null) Current state = FLUSHED, new state = CODING_END
2002-06-20 09:34:31 - Ctx( /struts-test ): IllegalStateException in: R(
/struts-test + /illegal1.jsp + null) Current state = FLUSHED, new state = CODING
2002-06-20 09:34:31 - Ctx( /struts-test ): IllegalStateException in: R(
/struts-test + /illegal1.jsp + null) Current state = FLUSHED, new state = CODING
...


The exceptions never stop and I have to restart Tomcat.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>