Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C6BEC9DCB for ; Thu, 13 Sep 2012 23:34:27 +0000 (UTC) Received: (qmail 58978 invoked by uid 500); 13 Sep 2012 23:34:24 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 58944 invoked by uid 500); 13 Sep 2012 23:34:24 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 58936 invoked by uid 99); 13 Sep 2012 23:34:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Sep 2012 23:34:24 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of DRuggeri@primary.net designates 216.87.38.218 as permitted sender) Received: from [216.87.38.218] (HELO mail2.primary.net) (216.87.38.218) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Sep 2012 23:34:16 +0000 Received: from home.simonrage.com ([216.114.77.126]:25760 helo=[192.168.0.2]) by mail2.primary.net with esmtpa (Exim 4.63) (envelope-from ) id 1TCIuw-0006gh-4I for users@httpd.apache.org; Thu, 13 Sep 2012 18:33:55 -0500 Message-ID: <50526D5D.9050206@primary.net> Date: Thu, 13 Sep 2012 18:33:49 -0500 From: Daniel Ruggeri User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: users@httpd.apache.org References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-ACL-Warn: X-The email account used to send this email was: DRuggeri@primary.net X-Spam-Score: -2.9 (--) X-Spam-Report: Spam detection software, running on the system "mail2.primary.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: On 9/13/2012 4:10 PM, Colin Murtaugh wrote: > I figured that might be the case; in this situation, the timeout is > due to the backend being slow. In particular, when I start up this > tomcat server, it starts accepting connections quite quickly, but it > may be 30-40 seconds before the app is fully loaded. It'd be great if > the proxy could recognize that it's not really ready yet and put the > node into the error state. [...] Content analysis details: (-2.9 points, 8.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] mod_proxy_balancer, balancer_manager questions On 9/13/2012 4:10 PM, Colin Murtaugh wrote: > I figured that might be the case; in this situation, the timeout is > due to the backend being slow. In particular, when I start up this > tomcat server, it starts accepting connections quite quickly, but it > may be 30-40 seconds before the app is fully loaded. It'd be great if > the proxy could recognize that it's not really ready yet and put the > node into the error state. Does it give a unique failure code? This is actually the use case that drove me to add the failonstatus option for ProxySet. For example, some containers return a 503 when the app is not yet initialized but the container is up. Granted, you will still have one failed connection per every X retry seconds, but in high-volume sites a few failures is much more appetizing than hundreds. -- Daniel Ruggeri --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org