[
https://issues.apache.org/jira/browse/ARTEMIS-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104762#comment-17104762
]
Justin Bertram commented on ARTEMIS-2754:
-----------------------------------------
FWIW, the behavior you're observing is outlined in [the
documentation|http://activemq.apache.org/components/artemis/documentation/latest/config-reload.html]
which states that when an existing {{divert}} is updated then there will be:
bq. No effect on the deployed divert (unless restarting broker, in which case
the divert will be redeployed)
Essentially the same is documented for when the filter is updated on a queue.
> Divert exclusivity can't be changed online via broker.xml
> ---------------------------------------------------------
>
> Key: ARTEMIS-2754
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2754
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.11.0
> Environment: Windows 10
> Oracle Java 1.8.0_144
> Reporter: Jan Šmucr
> Priority: Major
>
> Changing the
>
> {code:java}
> <exclusive>true</exclusive> {code}
> to
>
> {code:java}
> <exclusive>false</exclusive> {code}
> and vice versa in broker.xml does not change the exclusivity of the divert.
> The broker needs to be restarted in order for the change to be applied.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
