Uploaded image for project: 'ActiveMQ Artemis'
  1. ActiveMQ Artemis
  2. ARTEMIS-4629

Core bridge configuration validation errors

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 2.32.0
    • 2.33.0
    • Documentation
    • None
    • ActiveMQ Artemis 2.32.0, 2.31.2

      Operating systems: Windows, Linux

    Description

      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).

      Attachments

        1. working_example2.xml
          0.9 kB
          Aleksandr Milovidov
        2. working_example1.xml
          0.7 kB
          Aleksandr Milovidov
        3. non_working_example4.xml
          1 kB
          Aleksandr Milovidov
        4. non_working_example3.xml
          1 kB
          Aleksandr Milovidov
        5. example_validation_errors.log
          14 kB
          Aleksandr Milovidov

        Issue Links

          Activity

            People

              jbertram Justin Bertram
              aleksandr-milovidov Aleksandr Milovidov
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m