activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Leveque (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AMQ-6331) Honor excluded destinations in static routing on network connectors
Date Tue, 30 Aug 2016 17:25:20 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15449532#comment-15449532
] 

Xavier Leveque edited comment on AMQ-6331 at 8/30/16 5:24 PM:
--------------------------------------------------------------

According to the document about "Network of Brokers" (see http://activemq.apache.org/networks-of-brokers.html)

In NetworkConnector Properties table:
* *excludedDestinations:* _Destinations matching this list won't be forwarded across the network
(+this only applies to dynamicallyIncludedDestinations+)_

Also as seen at the end of this same documentation page:
* _Note that at the moment excludedDestinations property doesn't affect staticallyIncludedDestinations._

So, either you update this documentation page, or either you remove (cancel) this "improvement"
which caused me lot of problems when upgrading from AMQ 5.12.1 to 5.14 !!

In my case, I listed lot of queues and topics to exclude using wildcards, and only statically
included two queues. However the queues I want to include are covered by the exclusions. Before
this change it was not a problem, but now it is! What I was trying to achieve is to statically
specify only 2 queues to forward and make sure no other one will by dynamically included (by
default all queues and topics are dynamically included, which is something I do not want).
So I want to prevent any forwarding of any kind, except for the two specific queues I configured.
Maybe there is now another way to easily achieve that? Maybe with "staticBridge" set to true?





was (Author: the4summers):
According to the document about "Network of Brokers" (see http://activemq.apache.org/networks-of-brokers.html)

In NetworkConnector Properties table:
* *excludedDestinations:* _Destinations matching this list won't be forwarded across the network
(+this only applies to dynamicallyIncludedDestinations+)_

Also as seen at the end of this same documentation page:
* _Note that at the moment excludedDestinations property doesn't affect staticallyIncludedDestinations._

So, either you update this documentation page, or either you remove (cancel) this "improvement"
which caused me lot of problems when upgrading from AMQ 5.12.1 to 5.14 !!

In my case, I listed lot of queues and topics to exclude using wildcards, and only statically
included two queues. However the queues I want to include are covered by the exclusions. Before
this change it was not a problem, but now it is! What I was trying to achieve is to statically
specify only 2 queues to forward and make sure no other one will by dynamically included (by
default all queues and topics are dynamically included, which is something I do not want).
So I want to prevent any forwarding of any kind, except for the two specific queues I configured.
Maybe there is now another way to easily achieve that?



> Honor excluded destinations in static routing on network connectors
> -------------------------------------------------------------------
>
>                 Key: AMQ-6331
>                 URL: https://issues.apache.org/jira/browse/AMQ-6331
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.13.3
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.14.0
>
>
> When a destination is part of "staticallyIncludedDestinations" and "excludedDestinations"
then the "excludedDestinations" behaviour is not obeyed and the messages are forwarded to
the target AMQ instance.
> {code}
> <staticallyIncludedDestinations>
>   <queue physicalName="FOO.>"/>
> </staticallyIncludedDestinations>
> <excludedDestinations>
>   <queue physicalName="FOO.BAR" />
> </excludedDestinations>
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message