i still think its not the platform. My stuff worked fine until I used a
version of Apache with ssl, then I got the same problem as you. And
building mod_jserv from scratch did not help me either. I had to 'apxs it
in'. I don't know why it worked, or what it really did, but just rebuilding
mod_jserv.so and sticking it into libexec directory it did not work. it had
to be apxs-ed for some reason :). what do you mean apxs does not work
though? what kind of errors do you get? I think among other options you
have to say with EAPI also.
-----Original Message-----
From: Ritwick Dhar [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 27, 2000 10:42 AM
To: '[EMAIL PROTECTED]'
Subject: RE: HANDLER THREAD PROBLEM: Stream closed prematurely
Unfortunately, in my case, it doesn't work. The problem is compounded in my
case because my platform is AIX4.3.3 + IBM Apache 1.3.6.2 + Tomcat 3.1.
Something is seriously screwed up in this level of AIX.
apxs does not work. Period. No matter what I do.
I built IBM's version of apache from scratch with DSO support. Then I
downloaded Apache jServ and built that from scratch. This resulted in a new
mod_jserv.so. However, this one makes Apache core dump. So I'm back to
square one.
Can't believe its *this* difficult getting tomcat to run/build on AIX!!!
-----Original Message-----
From: Ranko Bijelonic [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 27, 2000 9:47 AM
To: [EMAIL PROTECTED]
Subject: RE: HANDLER THREAD PROBLEM: Stream closed prematurely
I had the exact same problem. Nothing helped until I recompiled mod_jserv
using the apache apxs utility.
So recompile, and everything should be fine.
-----Original Message-----
From: Ritwick Dhar [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 24, 2000 4:04 PM
To: '[EMAIL PROTECTED]'
Subject: RE: HANDLER THREAD PROBLEM: Stream closed prematurely
Update on this problem:
I simplified the client to simply POST a line of text and the server to
simply echo it back. The results seem to be:
The client can open an outputstream to a servlet and write to it, but a
close() or even a flush()
causes the stream to be shut down and the server prints the stacktrace for
an IOException. If the
stream is not flushed, however, the server proceeds without any input
whatsoever (contentlength = 0).
I tried this servlet on Jrun and WebSphere. Both work without a hitch.
I think this is starting to smell like a bug.
Thanks
Ritwick
-----Original Message-----
From: William Brogden [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 24, 2000 11:27 AM
To: [EMAIL PROTECTED]
Subject: Re: HANDLER THREAD PROBLEM: Stream closed prematurely
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
