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 capped the amount of data that the socket shutdown will read to 32k, and the total time to drain the socket to 2s. cheers tim On Mon, May 16, 2011 at 1:09 PM, verlag.preis...@t-online.de <verlag.preis...@t-online.de> wrote: > 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 the Redirector there. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
