Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 67274 invoked from network); 18 Feb 2011 19:24:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Feb 2011 19:24:40 -0000 Received: (qmail 46434 invoked by uid 500); 18 Feb 2011 19:24:36 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 46176 invoked by uid 500); 18 Feb 2011 19:24:34 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 46167 invoked by uid 99); 18 Feb 2011 19:24:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Feb 2011 19:24:33 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of francisboon@gmail.com designates 209.85.216.45 as permitted sender) Received: from [209.85.216.45] (HELO mail-qw0-f45.google.com) (209.85.216.45) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Feb 2011 19:24:25 +0000 Received: by qwk4 with SMTP id 4so3775340qwk.18 for ; Fri, 18 Feb 2011 11:24:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=tbB0e7kXu2mnODcrmjmEkE1G94/vcrrENzNhSlx2k9s=; b=eAAkmgCJqLok7P8OfM/+9b22+m+ZIIobDdwdHk029Gfs/6Mk796k/QzUM90+uJDGk+ GQGLb5JJhEiOdE1WdhL5vEBfszKh9KyMdrixc81R/5PFZrsEagYt0DqGeJUGY3pp0JDE FSDmLcYnnip2ifiEFD2471lC8aZlDxFqeyzMs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=gkUL7WjLhGrwww75PWqOr5Mptw2J6NoQfxOcr+447Y/rpI7kaHSodpLClOZXsxyulb 5B73DqOdNBi92sxLqw8CXtxgyYLNEC9qP4YHk+xPjqG0wu/wy3HfVsAydJqo2pSjkqZO dzMwV3JH9xPP1GEIYM94LEU/oXrnMPj1WexmI= MIME-Version: 1.0 Received: by 10.224.11.132 with SMTP id t4mr968770qat.323.1298057044255; Fri, 18 Feb 2011 11:24:04 -0800 (PST) Received: by 10.229.87.70 with HTTP; Fri, 18 Feb 2011 11:24:04 -0800 (PST) In-Reply-To: References: Date: Fri, 18 Feb 2011 19:24:04 +0000 Message-ID: Subject: proxy:ajp 'client denied by server configuration' when too many simultaneous requests happen From: Fran Boon To: users@tomcat.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org httpd error log: client denied by server configuration: proxy:ajp://localhost:8009/geoserver/gwc/service/wms This happens under 'high' load only: 1st few requests of a batch are answered but then they start dying - there are no bad URLs here. httpd snippet: ProxyPreserveHost on RewriteRule ^/geoserver/(.*)$ ajp://localhost:8009/geoserver/$1 [P] ProxyPassReverse /geoserver ajp://localhost:8009/geoserver/ =A0 =A0Order Allow,Deny =A0 =A0Allow from all =A0 I have tried these configuration options without any apparent difference: =A0 =A0ProxySet keepalive=3DOn timeout=3D15 ttl=3D60 Happens even with 'Allow from all' in proxy.conf (in fact nothing in that file makes any difference, presumably as it only affects Forward proxies. I have tried with both the default prefork MPM & also the worker MPM. Back-end is GeoServer in Tomcat 6 (exactly same thing happened with 5.5) on Debian Squeeze 64-bit & current Sun JVM. Nothing in the logs at the back-end, though, seems to be a problem with the Connector. Same thing whether or not using the 'APR based Apache Tomcat Native library 1.1.20' or not. I tried putting in a connectionTimeout into server.xml, but it makes no difference: Same with setting the minSpareThreads=3D"32" maxThreads=3D"256" to match those in apache.conf StartServers 2 MaxClients 256 MinSpareThreads 32 MaxSpareThreads 128 ThreadsPerChild 32 MaxRequestsPerChild 1024 None of these tuning options seem to make much difference. Only web posts I've seen are the on/off conditions rather than erratic ones= . Many thanks, for any suggestions :) Fran. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org