tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Plotnick" <>
Subject CoyoteWriter in error, never cleaned up
Date Thu, 19 Dec 2002 01:32:42 GMT
I'm using a rather complicated web page with two frames and
a jsp in both frames.

The upper frame has an applet, and the applet loads a
document by calling a servlet (in the same session as the page).

Clicking within the applet will cause new pages to load in the
lower page.

As a result of all this activity I seem to get the "Socket Error"
bug described in thread "Problem with Socket closing" and

Things would still not be too bad if the "CoyoteWriter" objects
were recycled. When the socket error occurs, the relevant 
"CoyoteWriter" objects get marked as being in error.

The problem is Tomcat (4.1.17 & 16) is still trying to reuse
these "CoyoteWriter" objects with the result of tomcat
returning blank pages to the browser.

CoyoteWriter does have a "isError()" method. A grep through
the source reveals nothing is ever calling this method.

It seems reasonable that after a socket write error, these
objects should get cleaned up and the application would
have a reasonable chance to recover.

I appreciate any insight and feedback on where these
"CoyoteWriter" objects should be managed.

Mark Plotnick
Ensodex, Inc.

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message