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 2003/01/16 02:08:38 UTC

DO NOT REPLY [Bug 16150] New: - IllegalStateException with Tomcat3.2.3 and JRE1.4.0_01

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

IllegalStateException with Tomcat3.2.3 and JRE1.4.0_01

           Summary: IllegalStateException with Tomcat3.2.3 and JRE1.4.0_01
           Product: Tomcat 3
           Version: 3.2.3 Final
          Platform: PC
        OS/Version: Other
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: Connectors
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: tchadha@cisco.com


The scenario is that I have a servlet/JSP which can be accessed by a link on a 
page, while this JSP/Servlet is being loaded(which might be a couple of 
seconds), if I access another link on the page or if I close the browser. I see 
the Tomcat service go into a loop. Following are the traces from Tomcat
 
2003-01-13 02:21:02 - Ctx( /webdialer ): IOException in: R( /webdialer 
+ /jsp/CallFailed.jsp + null) Connection reset by peer: socket write error
2003-01-13 02:21:02 - Ctx( /webdialer ): IllegalStateException in: R
( /webdialer + /jsp/CallFailed.jsp + null) Current state = FLUSHED, new state = 
CODING_END
2003-01-13 02:21:02 - Ctx( /webdialer ): IllegalStateException in: R
( /webdialer + /jsp/CallFailed.jsp + null) Current state = FLUSHED, new state = 
CODING
2003-01-13 02:21:02 - Ctx( /webdialer ): IllegalStateException in: R
( /webdialer + /jsp/CallFailed.jsp + null) Current state = FLUSHED, new state = 
CODING


The last two error messages are repeating a couple of thousand times, during 
which the Tomcat service takes up 100% CPU and if you repeat this scenario a 
couple of times the service just dies.
Interestingly, it is NOT an issue when we use JRE1.3.x. 
The same problem has been reported at multiple discussion groups, e.g., 
http://forum.java.sun.com/thread.jsp?thread=325460&forum=31&message=1328411
However, I did not see a solution to this problem.

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