Bug 54620 - [PATCH] custom mod_jk availability checks
Summary: [PATCH] custom mod_jk availability checks
Status: RESOLVED DUPLICATE of bug 54621
Alias: None
Product: Tomcat Connectors
Classification: Unclassified
Component: mod_jk (show other bugs)
Version: 1.2.37
Hardware: HP Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-28 13:19 UTC by Alan F
Modified: 2013-02-28 13:45 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alan F 2013-02-28 13:19:49 UTC
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,
Comment 1 Alan F 2013-02-28 13:45:16 UTC

*** This bug has been marked as a duplicate of bug 54621 ***