Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 31260 invoked from network); 4 Oct 2007 16:26:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Oct 2007 16:26:59 -0000 Received: (qmail 45854 invoked by uid 500); 4 Oct 2007 16:26:44 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 45817 invoked by uid 500); 4 Oct 2007 16:26:44 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 45806 invoked by uid 500); 4 Oct 2007 16:26:44 -0000 Delivered-To: apmail-jakarta-tomcat-dev@jakarta.apache.org Received: (qmail 45803 invoked by uid 99); 4 Oct 2007 16:26:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Oct 2007 09:26:44 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Oct 2007 16:26:46 +0000 Received: by brutus.apache.org (Postfix, from userid 33) id 6D5027141F2; Thu, 4 Oct 2007 09:26:26 -0700 (PDT) From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Subject: DO NOT REPLY [Bug 43553] New: - mod_jk 1.2.25 - Implement fail_on_status for workers inside mounts Message-ID: X-Bugzilla-Reason: AssignedTo Date: Thu, 4 Oct 2007 09:26:26 -0700 (PDT) X-Virus-Checked: Checked by ClamAV on apache.org DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=43553 Summary: mod_jk 1.2.25 - Implement fail_on_status for workers inside mounts Product: Tomcat 5 Version: Unknown Platform: Other OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: Connector:AJP AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: james_masson@yahoo.com Hi, this is from a conversation I had on tomcat-users with Rainer on 4th Oct 2007 I'd like to see a per-mount fail_on_status directive in mod_jk What happens currently with mod_jk 1.2.25: Currently, an entire worker gets dropped when the fail_on_status directive is triggered. Consider this example environment: 1x mod_jk apache instance 4x Tomcat server, each configured identically, running the same 6 web-apps With mod_jk set up as per the documentation, if I used fail_on_status, and it activated, a entire tomcat instance would be disabled. This takes out 5 perfectly functioning web-apps on the disabled server. A scenario could occur where 1 buggy web-app takes out the entire cluster, where the other 5 applications function perfectly. The ideal: Treat fail_on_status as per mount - so only single web-apps on a particular tomcat worker get taken out when it activates. Thanks for you efforts. If you need any help with testing, I have a few large multi-platform Tomcat farms. regards James Masson -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org