Bug 40637 - java.io.IOException: Stream closed / JspWriterImpl.java:203
Summary: java.io.IOException: Stream closed / JspWriterImpl.java:203
Status: RESOLVED INVALID
Alias: None
Product: Tomcat 5
Classification: Unclassified
Component: Jasper (show other bugs)
Version: 5.5.15
Hardware: PC Linux
: P3 minor (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL: http://www.citycarshare.org/
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-29 04:38 UTC by Bryce Nesbitt
Modified: 2006-10-17 19:45 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bryce Nesbitt 2006-09-29 04:38:35 UTC
I've been getting these exceptions in my logs for a while now.  I've done a LOT
of googling, but only find other people with these exceptions in their logs (and
no solutions).  I my case they seem to be causing "no harm" other than sysadmin
panic:


Sep 28, 2006 9:28:44 PM org.apache.jasper.runtime.PageContextImpl release
WARNING: Internal error flushing the buffer in release()
Sep 28, 2006 9:28:44 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet jsp threw exception
java.io.IOException: Stream closed
        at
org.apache.jasper.runtime.JspWriterImpl.ensureOpen(JspWriterImpl.java:203)
        at
org.apache.jasper.runtime.JspWriterImpl.clearBuffer(JspWriterImpl.java:159)
        at org.apache.jsp.index_jsp._jspService(org.apache.jsp.index_jsp:48)
        at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
        at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
        at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
        at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
        at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
        at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
        at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
        at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
        at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
        at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
        at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
        at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199)
        at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
        at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
        at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:684)
        at
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:876)
        at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
        at java.lang.Thread.run(Thread.java:595)


I guess I'm asking for a few more details, to be added in this exception, to
help all us folks track down the real cause.
Comment 1 Mark Thomas 2006-10-17 19:45:56 UTC
From the exceptino and lookingat the Tomcat source, you appear to be closing the
stream in your JSP which makes this a quesiton for the users list. If you are
100% sure you are not closing the stream feel free to re-open this bug and
provide the source for the simplest possible JSP that exhibit this issue.