https://issues.apache.org/bugzilla/show_bug.cgi?id=54620
Bug ID: 54620
Summary: [PATCH] custom mod_jk availability checks
Product: Tomcat Connectors
Version: 1.2.37
Hardware: HP
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mod_jk
Assignee: dev@tomcat.apache.org
Reporter: alan.fit...@igmarkets.com
Classification: Unclassified
Hi,
I've added a feature to mod_jk which provides an alternative to CPING/CPONG to
determine if a worker is "alive". It allows you to configure a URI to test
(using a GET request), and an expected HTTP status code.
worker.tomcat_default.custom_check_expected_status=200
worker.tomcat_default.custom_check_uri=/app/somefile
The reason for this is that we do rolling deploys across a cluster of Tomcat
servers, and in the time the app is redeploying mod_jk continues to route
requests to the Tomcat instance, resulting in 404's to our clients.
Is this something which would be considered for inclusion in mod_jk? Does it
need more work?
Thanks and Best Regards,
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
