Does your client close the stream that writes the request or
just flush it? I seem to recall having a problem similar to this
where the solution was to not close the client's output stream
until after the complete transaction.
Ritwick Dhar wrote:
>
> Hi,
>
> This problem is driving me nuts. I've tried debugging this, but nothing yet.
> I was hoping someone on this list will have come accross this before.
>
> Case: I have a servlet (server) that accepts POST requests (content-type=
> application/x-ofx), and sends back a OFX response. I have another servlet
> (client), that opens a URL to the server, writes the request, and reads the
> reponse. Simple.
>
> The problem is, the moment the client tries to call
> 'urlConn.getInputStream()' to get an inputstream from the server, I get this
> (on the server console):
>
> HANDLER THREAD PROBLEM: java.io.IOException: Stream closed prematurely
> java.io.IOException: Stream closed prematurely
> at java.lang.Throwable.<init>(Compiled Code)
> at java.lang.Exception.<init>(Compiled Code)
> at java.io.IOException.<init>(Compiled Code)
> at
> org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Comp
> iled Code)
> at
> org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection
> (Compiled Code)
> at org.apache.tomcat.service.TcpConnectionThread.run(Compiled Code)
> at java.lang.Thread.run(Compiled Code)
>
> What's really driving me up the wall is that this works perfectly fine with
> Both WebSphere and JRun. Is this something particular to Tomcat??
>
> Thanks for all help
>
> Rit
--
WBB - [EMAIL PROTECTED]
Author of Java Developer's Guide to Servlets and JSP
ISBN 0-7821-2809-2
