You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Roddie Kieley (JIRA)" <ji...@apache.org> on 2018/07/31 12:23:00 UTC

[jira] [Created] (ARTEMIS-2000) scaleDown/scaledownconnector call does not take routing type into account when creating queues on addresses

Roddie Kieley created ARTEMIS-2000:
--------------------------------------

             Summary: scaleDown/scaledownconnector call does not take routing type into account when creating queues on addresses
                 Key: ARTEMIS-2000
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2000
             Project: ActiveMQ Artemis
          Issue Type: Bug
          Components: Broker
    Affects Versions: 2.6.1
         Environment: Fedora 27

OpenJDK 1.8.0_172-b11

master commit f0c13622ac7e821a81a354b0242ef5235b6e82df
            Reporter: Roddie Kieley


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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)