DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43553>.
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
|