Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4E11FE41.2030008@apache.org>
Date: Mon, 04 Jul 2011 18:54:09 +0100
From: Mark Thomas <markt@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-GB;
 rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Multiple errors (regressions) on Tomcat 7.0.17
References: <002701cc3980$5c83a430$158aec90$@preisser@t-online.de>
 <4E1070E7.9050701@apache.org>
 <000001cc398b$90f42ae0$b2dc80a0$@preisser@t-online.de>
 <4E11E2AC.8020008@apache.org>
In-Reply-To: <4E11E2AC.8020008@apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 04/07/2011 16:56, Mark Thomas wrote:
> On 03/07/2011 15:14, eurotrans-Verlag wrote:
>>>> 2) When using the ISAPI Redirector 1.2.32 and Tomcat Native 1.1.20
>>> which is
>>>> included in the windows distribution, I get these errors when a
>>> client makes
>>>> a request to IIS which is redirected to Tomcat, resulting in 100% CPU
>>> usage
>>>> by tomcat's process:
>>>
>>> Under what circumstances? Some requests, all requests? The APR/native
>>> AJP connector works with mod_jk and mod_proxy_ajp on linux so it looks
>>> like either the ISAPI redirector is sending something unexpected that
>>> isn't handled well or the windows specific code in the APR/native
>>> connector isn't handling something.
>>
>> For this test, I downloaded the Tomcat 7.0.17 (windows 64 bit) and extracted
>> it to a directory. I didn't changed anything in the Tomcat directory (also
>> not the config files). I set the ISAPI Redirector 1.2.32 to redirect all
>> requests to Tomcat on port 8009, using ajp13.
> 
> OK. I've set up IIS 7 and Tomcat 7.0.17 and I see the same thing.
> 
> There has been some refactoring of the connector code but (famous last
> words) it should have been harmless. I'm looking at this now...

The problem has been found and fixed. I'm leaning towards stopping the
7.0.17 release and re-starting with a 7.0.18 tag.

Mark


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org