et and do not find useful information about how to
> solve it.
>
> Your advice is appreciated.
>
> Thanks
>
> Guofeng
>
> 2012-04-25 15:47:59,679 INFO [STDE] java.io.IOException: Stream closed
> 2012-04-25 15:47:59,679 INFO [STDE] at
> org.apache.jasper.runti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leonard,
On 7/20/2009 6:15 PM, Leonard Gestrin wrote:
> In my application I have servlet filter that handles error
> handling for runtime exceptions; when such exception happens, it
> forwards request to error page where user-frienldy error is
> prese
clude"? This is 6.x version of tomcat.
Caused by: java.io.IOException: Stream closed
at
org.apache.jasper.runtime.JspWriterImpl.ensureOpen(JspWriterImpl.java:204)
at
org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:115)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan,
Schuster Stefan wrote:
> As far as I can tell, the XML-Beans generated code works well - even if
> The stream is closed after reading, this should be no problem as the next
> request will submit a new stream, right?
Yes, your servlet can clos
PROTECTED]
Gesendet: Freitag, 5. Dezember 2008 17:43
An: Tomcat Users List
Betreff: Re: AW: AW: java.io.IOException: Stream closed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan,
Schuster Stefan wrote:
> The code reading the stream is generated by XMLBeans.
>
> Is there something that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan,
Schuster Stefan wrote:
> The code reading the stream is generated by XMLBeans.
>
> Is there something that I should not do with the stream? For example
> closing it or something like that?
You shouldn't have to do anything like that.
> <<>
e(response);
} catch (Exception ex) {
ex.printStackTrace();
return null;
}
}
}
-Ursprüngliche Nachricht-
Von: Christopher Schultz [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 4. Dezember 2008 23:22
An: Tomcat Users List
Be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stafan,
Schuster Stefan wrote:
> I still have the problem mentioned below. I just don't have any idea
> where to start with problem solving? Can it be a problem in Tomcat? I guess
> not as this is a very simple use-case (read the stream in the servle
That's odd.
> Every second call results in the following exception:
>
> java.io.IOException: Stream closed
> at org.apache.catalina.connector.InputBuffer.read(InputBuffer.java:325)
> at
> org.apache.catalina.connector.CoyoteInputStream.read(Coy
lease?
Thanks
Stefan
-Ursprüngliche Nachricht-
Von: Schuster Stefan [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 2. Dezember 2008 15:24
An: users@tomcat.apache.org
Betreff: java.io.IOException: Stream closed
Hi everybody,
I have the following problem with tomcat 6.0.18:
I wrote a servlet
Hi everybody,
I have the following problem with tomcat 6.0.18:
I wrote a servlet that reads the input stream with
XML Beans. An application sends requests to the servlet, but only the first
request succeedes. Every
Second call results in the following exception:
java.io.IOException: Stream
use of the problem and how to fight it ?
We use JBoss 4.0.3 bundled with Tomcat5.5.9, and here's the exception
(found many times in application log file)
java.io.IOException: Stream closed
at
org.apache.jasper.runtime.BodyContentImpl.ensureOpen(BodyContentImpl.
12 matches
Mail list logo
