You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by jf...@apache.org on 2019/07/30 14:22:03 UTC
[tomcat] branch master updated: Clarify the logic of the health
check.
This is an automated email from the ASF dual-hosted git repository.
jfclere pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/master by this push:
new 425b037 Clarify the logic of the health check.
425b037 is described below
commit 425b037f0d78370211afdf56a05190ca512ce830
Author: Jean-Frederic Clere <jf...@gmail.com>
AuthorDate: Tue Jul 30 16:21:14 2019 +0200
Clarify the logic of the health check.
---
webapps/docs/config/valve.xml | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/webapps/docs/config/valve.xml b/webapps/docs/config/valve.xml
index 06dae09..3b889a3 100644
--- a/webapps/docs/config/valve.xml
+++ b/webapps/docs/config/valve.xml
@@ -2093,7 +2093,10 @@
<subsection name="Introduction">
<p>The <strong>Health Check Valve</strong> responds to
- cloud orchestrators health checks</p>
+ cloud orchestrators health checks. Note that it checks
+ that a context is mapped (so that an application is deployed),
+ for example if you don't have a ROOT context but demo-1.0
+ you have to check for <code>/demo-1.0/health</code></p>
</subsection>
<subsection name="Attributes">
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org