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 2004/02/24 19:53:44 UTC

DO NOT REPLY [Bug 27197] New: - "SEVERE: Error finishing response" on any requests, fixed by server restart

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

"SEVERE: Error finishing response" on any requests, fixed by server restart

           Summary: "SEVERE: Error finishing response" on any requests,
                    fixed by server restart
           Product: Tomcat 5
           Version: 5.0.16
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Connector:Coyote
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: tidoublemy@yahoo.com


Without any apparent trigger, the server went unresponsive, spewing exceptions 
like the following whenever a request was made (servlet or JSP):

Feb 24, 2004 11:29:22 AM org.apache.coyote.http11.Http11Processor process
SEVERE: Error finishing response
java.lang.ClassCastException
	at org.apache.coyote.http11.filters.GzipOutputFilter.end
(GzipOutputFilter.java:165)
	at org.apache.coyote.http11.InternalOutputBuffer.endRequest
(InternalOutputBuffer.java:439)
	at org.apache.coyote.http11.Http11Processor.process
(Http11Processor.java:842)
	at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnectio
n(Http11Protocol.java:696)
	at org.apache.tomcat.util.net.TcpWorkerThread.runIt
(PoolTcpEndpoint.java:605)
	at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
(ThreadPool.java:677)
	at java.lang.Thread.run(Thread.java:536)

After restarting Tomcat, the problem went away and has not, thus far, 
resurfaced.  It had been running fine for several weeks before this problem, 
with no configuration changes.  This is the first time I've ever seen this 
problem.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org