tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 50839] Closing connection on the client side (browser) during unfinished transmission result in 100% CPU slike for 30 sec during socket shutdownd in jk_connect.c
Date Mon, 16 May 2011 01:19:28 GMT

--- Comment #3 from Konstantin Prei├čer <> 2011-05-16 01:19:28 UTC ---

I could also observe this issue using Windows Server 2008 SP2 (32 bit), IIS
7.0, ISAPI Redirector 1.2.31. It happened when a Servlet was producing lots of
data, a client made a request to this servlet and canceled the download a few
seconds later. This was leading to 100% CPU usage for about 30 seconds.

I reported this issue on the users list [1] where Tim Whittington pointed me to
this bug and asked me to attach a TRACE level log file.

To do this, I made a jsp (download3.jsp in the attachment) which produces about
32 MB of random data and writes it to the client. I also made a Downloader
( which uses a URLConnection to make a request to the
servlet and download it slowly, and abort the connection after 2400 bytes are
read. The log of this Downloader is in SlowDownloader.log, the log of the JSP
is in JSPLog.log.

isapi_redirect.log contains the logfile of the ISAPI redirector with TRACE log


Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message