[
https://issues.apache.org/jira/browse/ARTEMIS-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17698456#comment-17698456
]
ASF subversion and git services commented on ARTEMIS-4190:
----------------------------------------------------------
Commit 7a0bf52ed830cd9cb870efe00c9ef8265c2ab793 in activemq-artemis's branch
refs/heads/main from Domenico Francesco Bruscino
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=7a0bf52ed8 ]
ARTEMIS-4190 Fix config-delete-queues when address changes
> config-delete-queues doesn't always work as expected
> ----------------------------------------------------
>
> Key: ARTEMIS-4190
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4190
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Domenico Francesco Bruscino
> Assignee: Domenico Francesco Bruscino
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Setting config-delete-queues + config-delete-addresses seems not to work as
> expected in the use case where the original multicast address remains, but
> the fixed queues within the multicast address are moved to anycast addresses.
> Consider the following case:
> We start with two multicast addresses, like so:
> {code:xml}
> <addresses xmlns="urn:activemq:core">
> <address name="DLQ">
> <anycast>
> <queue name="DLQ" />
> </anycast>
> </address>
> <address name="ExpiryQueue">
> <anycast>
> <queue name="ExpiryQueue" />
> </anycast>
> </address>
> <address name="TEST.QUEUE.0">
> <multicast>
> <queue name="TEST.QUEUE.0.1"/>
> <queue name="TEST.QUEUE.0.2"/>
> </multicast>
> </address>
> <address name="TEST.QUEUE.1">
> <multicast>
> <queue name="TEST.QUEUE.1.1"/>
> <queue name="TEST.QUEUE.1.2"/>
> </multicast>
> </address>
> </addresses>
> {code}
> We change the addresses to move the internal queues out of the multicast
> addresses and to anycast addresses, but keeping the original multicast
> addresses themselves, like so:
> {code:xml}
> <addresses xmlns="urn:activemq:core">
> <address name="DLQ">
> <anycast>
> <queue name="DLQ" />
> </anycast>
> </address>
> <address name="ExpiryQueue">
> <anycast>
> <queue name="ExpiryQueue" />
> </anycast>
> </address>
> <address name="TEST.QUEUE.0">
> <multicast>
> <queue name="TEST.QUEUE.0"/>
> </multicast>
> </address>
> <address name="TEST.QUEUE.1">
> <multicast>
> <queue name="TEST.QUEUE.1"/>
> </multicast>
> </address>
> <address name="TEST.QUEUE.0.1">
> <anycast>
> <queue name="TEST.QUEUE.0.1"/>
> </anycast>
> </address>
> <address name="TEST.QUEUE.0.2">
> <anycast>
> <queue name="TEST.QUEUE.0.2"/>
> </anycast>
> </address>
> <address name="TEST.QUEUE.1.1">
> <anycast>
> <queue name="TEST.QUEUE.1.1"/>
> </anycast>
> </address>
> <address name="TEST.QUEUE.1.2">
> <anycast>
> <queue name="TEST.QUEUE.1.2"/>
> </anycast>
> </address>
> </addresses>
> {code}
> We end up with the queues remaining in the multicast addresses, along with
> new anycast queues of the same name as anycast queues.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
