tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 13759] - Tomcat Coyote hangs at fill() spending 100% CPU
Date Tue, 05 Nov 2002 11:33:23 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13759>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13759

Tomcat Coyote hangs at fill() spending 100% CPU

vicentesalvador@netscape.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From vicentesalvador@netscape.net  2002-11-05 11:33 -------
On JDK Api Docs, about InputStream.read():

If len is zero, then no bytes are read and 0 is returned; otherwise, there is an
attempt to read at least one byte. If no byte is available because the stream is
at end of file, the value -1 is returned; otherwise, at least one byte is read
and stored into b. 

So a 0 and a -1 can be returned by read() and it means that there is not more
data available, so I think we just should disconnect.

Surelly this is causing the bug, because if 0 or -1 is returned, then lastValid
variable is not updated and doRead stands calling fill() forever.

Now I will reopen the bug... If you don't agree, feel free to resolve it again!!!

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message