>
> That's a really wierd problem.
> Do you mean that it also happen with TC 4 built-in static page serving ? Or
> is it just with Slide ?
It's not easily reproducible on-demand, and at the moment everything is
going through slide, I think - so I can't really say.
>
> There is a setSoTimeout(60000) on the socket, so if something (Slide, the TC
> connector) hangs, or something really bad happens, the socket will be
> flushed and closed. I assume here, something really bad happens, but after
> 60s the remaining bytes are sent (here, it's the termination chunk).
>
This would explain the problem, though not why something is happening to
begin with.
>
> I would say it's a Tomcat 4 problem (bad luck, I still get to fix the bug,
> since I wrote most of the connector), and it would be very important to fix
> it.
I thought there was a good chance of it being a tc4 problem, but I'm not
on any of the tomcat lists, and there was a good chance that it was
slide at fault, so I asked here.
>
> I think we should try to narrow the problem a little bit.
> I assume you're running the Slide version from CVS.
Yes, slide cvs from (I think) yesterday.
> Here's what you could try to help me isolate the problem :
> - Update to the latest nigthly build of TC 4.0. We're a couple days away
> from b2, so it's supposed to be stable, and it has a lot of very important
> fixes introduced since b1.
I was using m5, before upgrading to b1 yesterday, so it's not a new
problem - but I'll try the latest nightly build. Since it is hard to
reproduce it might be a couple of days before I can say anything for
sure.
> - If it still fails, try with the HTTP/1.0 connector. By default, it's
> commented out in the conf/server.xml. If it fixes the problem, then it's a
> problem somewhere in the HTTP/1.1 connector.
I'll try that too.
Michael
