Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 59581 invoked from network); 28 Feb 2011 15:51:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Feb 2011 15:51:19 -0000 Received: (qmail 22979 invoked by uid 500); 28 Feb 2011 15:51:15 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 22571 invoked by uid 500); 28 Feb 2011 15:51:12 -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 22561 invoked by uid 99); 28 Feb 2011 15:51:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Feb 2011 15:51:10 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=FREEMAIL_FROM,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Feb 2011 15:51:04 +0000 Received: from isper.nabble.com ([192.168.236.156]) by sam.nabble.com with esmtp (Exim 4.69) (envelope-from ) id 1Pu5Mx-0003BI-5K for users@tomcat.apache.org; Mon, 28 Feb 2011 07:50:43 -0800 Message-ID: <31030814.post@talk.nabble.com> Date: Mon, 28 Feb 2011 07:50:43 -0800 (PST) From: laredotornado To: users@tomcat.apache.org Subject: Detecting resource usage MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: laredotornado@gmail.com X-Virus-Checked: Checked by ClamAV on apache.org Hi, We are using Tomcat 6.0.24 running on two different machines. In our workers.properties file, we have worker.worker1.fail_on_status=500,503 to cause instances to gracefully fail over if there is a problem on one instance. This is great, but if one app server is repeatedly failing over to the second app server (in which case only one is handling all our traffic), how can we pro-actively detect that there is a problem with the first app server? Thanks, - Dave -- View this message in context: http://old.nabble.com/Detecting-resource-usage-tp31030814p31030814.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org