Apache
/
activemq-artemis
mirror of https://github.com/apache/activemq-artemis.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

NO-JIRA remove failover-on-server-shutdown from bridge doc

This commit is contained in:
Justin Bertram 2021-02-07 14:48:13 -06:00 committed by Clebert Suconic
parent 2c11c2e3e8
commit 86cb888b62
2 changed files with 3 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
artemis-server/src/main/resources/schema/artemis-configuration.xsd
View File

@ -1589,7 +1589,9 @@
<xsd:element name="failover-on-server-shutdown" type="xsd:boolean" default="false" maxOccurs="1" minOccurs="0"> <xsd:element name="failover-on-server-shutdown" type="xsd:boolean" default="false" maxOccurs="1" minOccurs="0">
<xsd:annotation> <xsd:annotation>
<xsd:documentation> <xsd:documentation>
should failover be prompted if target server is cleanly shutdown? DEPRECATED: This setting has no impact, but it's being left here to avoid XML parsing errors for users
who still have it set. Failover on shutdown is controlled via the ha-policy set on the *broker* to
which the bridge connects.
</xsd:documentation> </xsd:documentation>
</xsd:annotation> </xsd:annotation>
</xsd:element> </xsd:element>

17
docs/user-manual/en/core-bridges.md
View File

@ -132,23 +132,6 @@ Let's take a look at all the parameters in turn:
value of `-1` signifies an unlimited number of attempts. The default value is value of `-1` signifies an unlimited number of attempts. The default value is
`-1`. `-1`.
- `failover-on-server-shutdown`. This optional parameter determines whether the
bridge will attempt to failover onto a backup server (if specified) when the
target server is cleanly shutdown rather than crashed.
The bridge connector can specify both a live and a backup server, if it
specifies a backup server and this parameter is set to `true` then if the
target server is *cleanly* shutdown the bridge connection will attempt to
failover onto its backup. If the bridge connector has no backup server
configured then this parameter has no effect.
Sometimes you want a bridge configured with a live and a backup target
server, but you don't want to failover to the backup if the live server is
simply taken down temporarily for maintenance, this is when this parameter
comes in handy.
The default value for this parameter is `false`.
- `use-duplicate-detection`. This optional parameter determines whether the - `use-duplicate-detection`. This optional parameter determines whether the
bridge will automatically insert a duplicate id property into each message bridge will automatically insert a duplicate id property into each message
that it forwards. that it forwards.