| Summary: | [PATCH] custom mod_jk availability checks | ||
|---|---|---|---|
| Product: | Tomcat Connectors | Reporter: | Alan F <alan.fitton> |
| Component: | mod_jk | Assignee: | Tomcat Developers Mailing List <dev> |
| Status: | NEW --- | ||
| Severity: | enhancement | CC: | gerhardus.geldenhuis, tim.einmahl |
| Priority: | P2 | Keywords: | PatchAvailable |
| Version: | 1.2.37 | ||
| Target Milestone: | --- | ||
| Hardware: | HP | ||
| OS: | Linux | ||
| Attachments: | Patch to add custom ping feature | ||
*** Bug 54620 has been marked as a duplicate of this bug. *** *** Bug 46676 has been marked as a duplicate of this bug. *** |
Created attachment 30004 [details] Patch to add custom ping feature 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,