I think the problem is from some bugs in IE's HTTP/1.1 impl, which Apache
out-of-box downgrades to a 1.0 conversation. Are you seeing this with TC
standalone or with Apache in front of it?
But the CPU util is definitely a bug.
On Thu, 18 Jan 2001, Graham Wright wrote:
> The problem does seem to be caused by IE but also varies depending of
> the version and service pack of Windows being used to run IE.
>
> The error itself does not cause problems but it seems to be occasionly
> causing Tomcat 3.2.1 to go into a 100% cpu cycle from which it never
> recovers.
>
> Graham
>
>
> Hans Bergsten wrote:
>
> > [EMAIL PROTECTED] wrote:
> >
> >> Hello,
> >>
> >> sorry for posting this issue on the dev list, but on the user list no one
> >> has an idea about a solution and so I thought you guys should take care and
> >> provide an answer to the user list.
> >>
> >> This is the error message on the console:
> >> 2001-01-17 01:29:59 - Ctx( ): IOException in: R( + cocoon/back.gif +
> >> null)socket write error (code=10053)
> >> The page is displayed correctly so what is wrong?
> >>
> >> See the attached files.
> >> Configuration: WinNT, Tomcat 3.2.1 (stand alone), Cocoon 1.8
> >
> >
> > I have seen this when using Internet Explorer (IE) and the resource
> > is cached by IE. It seems like IE closes the connection before reading
> > the complete response in this case, so Tomcat complains that it
> > couldn't write the full response. I don't see a way to fix this at
> > the Tomcat end.
> >
> > Hans
>
>
>
--
Nicolaus Bauman
Software Engineer
Simplexity Systems
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
