This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new 406b09b Document update (#4195)
406b09b is described below
commit 406b09b1d7eaae51046c5ab831f8ab53ac3a71e6
Author: Nitesh Koushik S <[email protected]>
AuthorDate: Fri Sep 11 15:46:56 2020 +0530
Document update (#4195)
From singular to plural, is to are
---
.../src/main/docs/modules/eips/pages/failover-eip.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/core/camel-core-engine/src/main/docs/modules/eips/pages/failover-eip.adoc
b/core/camel-core-engine/src/main/docs/modules/eips/pages/failover-eip.adoc
index ecc36a1..98be858 100644
--- a/core/camel-core-engine/src/main/docs/modules/eips/pages/failover-eip.adoc
+++ b/core/camel-core-engine/src/main/docs/modules/eips/pages/failover-eip.adoc
@@ -15,7 +15,7 @@ The Failover EIP supports 4 options which are listed below:
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *exception* | A list of class names for specific exceptions to monitor. If
no exceptions is configured then all exceptions is monitored | | List
+| *exception* | A list of class names for specific exceptions to monitor. If
no exceptions are configured then all exceptions is monitored | | List
| *roundRobin* | Whether or not the failover load balancer should operate in
round robin mode or not. If not, then it will always start from the first
endpoint when a new message is to be processed. In other words it restart from
the top for every message. If round robin is enabled, then it keeps state and
will continue with the next endpoint in a round robin fashion. You can also
enable sticky mode together with round robin, if so then it will pick the last
known good endpoint to use wh [...]
| *sticky* | Whether or not the failover load balancer should operate in
sticky mode or not. If not, then it will always start from the first endpoint
when a new message is to be processed. In other words it restart from the top
for every message. If sticky is enabled, then it keeps state and will continue
with the last known good endpoint. You can also enable sticky mode together
with round robin, if so then it will pick the last known good endpoint to use
when starting the load balanci [...]
| *maximumFailoverAttempts* | A value to indicate after X failover attempts we
should exhaust (give up). Use -1 to indicate never give up and continuously try
to failover. Use 0 to never failover. And use e.g. 3 to failover at most 3
times before giving up. his option can be used whether or not roundRobin is
enabled or not. | -1 | String
