[
https://issues.apache.org/jira/browse/ARTEMIS-4629?focusedWorklogId=903405&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-903405
]
ASF GitHub Bot logged work on ARTEMIS-4629:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 02/Feb/24 17:58
Start Date: 02/Feb/24 17:58
Worklog Time Spent: 10m
Work Description: jbertram merged PR #4802:
URL: https://github.com/apache/activemq-artemis/pull/4802
Issue Time Tracking
-------------------
Worklog Id: (was: 903405)
Time Spent: 20m (was: 10m)
> Core bridge configuration validation errors
> -------------------------------------------
>
> Key: ARTEMIS-4629
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4629
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 2.32.0
> Environment: ActiveMQ Artemis 2.32.0, 2.31.2
> Operating systems: Windows, Linux
> Reporter: Aleksandr Milovidov
> Priority: Minor
> Attachments: example_validation_errors.log, non_working_example3.xml,
> non_working_example4.xml, working_example1.xml, working_example2.xml
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When I tried to configure Core Bridge to transfer messages from one Artemis
> broker to another clustered Artemis broker, I have encountered several
> validation errors. I tried to insert ha option in different positions in the
> bridge section and got different validation errors. It seems that order of
> parameters in the bridge section does matter and it is impossible to combine
> ha options with reconnect parameters.
> Attached examples of working and non-working bridge configurations (it needs
> to be added to default broker.xml).
> Example core bridge configuration from documentation also does not work.
> There are also undocumented parameters which are mentioned in error log
> message, for example "reconnect-attempts-same-node". It is documented only in
> configuration index (does not exists in
> [https://activemq.apache.org/components/artemis/documentation/latest/core-bridges.html]).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)