You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/07/31 12:37:00 UTC
[jira] [Commented] (ARTEMIS-2000) scaleDown/scaledownconnector call
does not take routing type into account when creating queues on addresses
[ https://issues.apache.org/jira/browse/ARTEMIS-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563593#comment-16563593 ]
ASF GitHub Bot commented on ARTEMIS-2000:
-----------------------------------------
GitHub user RoddieKieley opened a pull request:
https://github.com/apache/activemq-artemis/pull/2202
ARTEMIS-2000: For ScaleDown set the RoutingType header property on th…
…e message so if the address does not exist on the other end it will be created correctly.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/RoddieKieley/activemq-artemis ARTEMIS-2000
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/2202.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2202
----
commit 71f75e2ded2fe5f61e7099848b571e993f9ebbea
Author: Roddie Kieley <rk...@...>
Date: 2018-07-31T12:34:56Z
ARTEMIS-2000: For ScaleDown set the RoutingType header property on the message so if the address does not exist on the other end it will be created correctly.
----
> 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
> Priority: Major
>
> 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)