It looks like this is a regression in 1.2.31 - the socket shutdown
code that drained the response message from the AJP socket before
closing it was mis-counting the bytes read, causing a CPU busy loop
until it hit a 30 second cap on lingering byte reads.
I've committed a fix for 1.2.32 and also
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 5/14/2011 4:01 PM, André Warnier wrote:
eurotrans-Verlag wrote:
However I would expect write() to always throw an IOException when the
connection to the client is aborted,
Remember, there are 2 separate connections : the connection
This sounds like https://issues.apache.org/bugzilla/show_bug.cgi?id=50839
If you can capture a TRACE level log form the Tomcat Connector
(configure in isapi_redirect.properties) and attach it to the bug,
I'll take a look.
cheers
tim
On Sun, May 15, 2011 at 1:20 AM, eurotrans-Verlag
Hi Tim,
This sounds like
https://issues.apache.org/bugzilla/show_bug.cgi?id=50839
If you can capture a TRACE level log form the Tomcat Connector
(configure in isapi_redirect.properties) and attach it to the bug,
I'll take a look.
cheers
tim
Thanks! I will attach a Trace level log from
eurotrans-Verlag wrote:
Hello everybody,
I stumbled upon a strange problem with the ISAPI Redirector 1.2.31 on
Windows Server 2008 SP2 (32 bit) with IIS 7.0. The problem is, that when a
Servlet is generating lots of data (e.g. 200 MB) and a user downloads it
over the Isapi Redirector/IIS7, and
Hi André, thanks for your reply.
To figure out if this is what's happening, you could do some logging at
the servlet end,
to see if it keeps sending data even when the client has canceled, or
if it itself gets
some stop indication from the isapi_redirector (also a closed socket
e.g.).
Or
eurotrans-Verlag wrote:
Hi André, thanks for your reply.
To figure out if this is what's happening, you could do some logging at
the servlet end,
to see if it keeps sending data even when the client has canceled, or
if it itself gets
some stop indication from the isapi_redirector (also a
