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

scaleDown/scaledownconnector call does not take routing type into account when creating queues on addresses

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.6.1
    • 2.6.4, 2.7.0
    • Broker
    • None
    • Fedora 27

      OpenJDK 1.8.0_172-b11

      master commit f0c13622ac7e821a81a354b0242ef5235b6e82df

    Description

      In testing this functionality, if the second broker has messages while the first does not have the address for those messages created, upon scaledown of the second broker we see that when the address is created it always has the default *CAST configuration of MULTICAST.

      E.g. if you use the web console to create an anycast address with an anycast queue, then use the web console to send a single message to that queue, when scale down is executed the other broker will then have an anycast address with a multicast queue.

      Attachments

        Activity

          People

            Unassigned Unassigned
            rkieley Roddie Kieley
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: