You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Geurt Schimmel <GS...@schubergphilis.com> on 2012/11/01 00:45:53 UTC
Whitelisting forwarded queues
BrokerA is forwarding a number of queues with <staticallyIncludedDestinations> to BrokerB.
How can BrokerB prevent BrokerA from relentlessly forwarding whatever BrokerA likes (and only allow the queues to be forwarded that were agreed) using Spring XML ?
Thanks.
Re: Whitelisting forwarded queues
Posted by James Green <ja...@gmail.com>.
By forwarding ">", everything will be broadcast. Limit it to down to
suppress. The discussion I linked to was that without a destinationFilter
set, subscription traffic was being forwarded at all times.
The documentation could be improved to be a lot more concise but I don't
think edits are open to the public.
On 1 November 2012 10:29, Geurt Schimmel <GS...@schubergphilis.com>wrote:
> No, this is another issue I think.
> When I configure my broker to forward ">" to you, and you only expect and
> process the queue "TEST.FOO", it might get messy on your broker (in the
> best case with a few messages to a few queues, in the worst case, your
> broker will become unresponsive). Sure, if you are aware of the unsolicited
> forwarding the network-traffic has already occurred, but you want to keep
> your broker alive and clean. So I'm looking for a solution for that problem.
>
> Geurt
>
> -----Original Message-----
> From: James Green [mailto:james.mk.green@gmail.com]
> Sent: Thursday, November 01, 2012 8:35 AM
> To: users@activemq.apache.org
> Subject: Re: Whitelisting forwarded queues
>
> Are you referring to this discussion, had only days ago?
>
>
> http://mail-archives.apache.org/mod_mbox/activemq-users/201210.mbox/%3CCAMH6+azsejiNB8zadd5_VYo0U_9Y-42Uyg+7YC6To7zt+k5Zxw@mail.gmail.com%3E
>
>
> On 31 October 2012 23:45, Geurt Schimmel <GSchimmel@schubergphilis.com
> >wrote:
>
> > BrokerA is forwarding a number of queues with
> > <staticallyIncludedDestinations> to BrokerB.
> > How can BrokerB prevent BrokerA from relentlessly forwarding whatever
> > BrokerA likes (and only allow the queues to be forwarded that were
> > agreed) using Spring XML ?
> >
> > Thanks.
> >
> >
>
Re: Whitelisting forwarded queues
Posted by Geurt Schimmel <GS...@schubergphilis.com>.
Thanks ! I'm sure IT-auditors will raise this kind of questions...
On 1 nov. 2012, at 12:03, "Gary Tully" <ga...@gmail.com> wrote:
> the default for a network bridge is to forward on demand, so when
> there is a remote consumer. In this way, only destinations that have
> remote consumers will get messages
> forwarded.
> with staticallyIncludedDestinations, you say, create a local consumer
> for this destination and forward irrespective of demand. so always
> forward.
> So if you only want to have TEST.FOO forwarded because that is the
> only destination that has consumers on it, using the default demand
> forwarding will work fine.
>
> On 1 November 2012 10:29, Geurt Schimmel <GS...@schubergphilis.com> wrote:
>> No, this is another issue I think.
>> When I configure my broker to forward ">" to you, and you only expect and process the queue "TEST.FOO", it might get messy on your broker (in the best case with a few messages to a few queues, in the worst case, your broker will become unresponsive). Sure, if you are aware of the unsolicited forwarding the network-traffic has already occurred, but you want to keep your broker alive and clean. So I'm looking for a solution for that problem.
>>
>> Geurt
>>
>> -----Original Message-----
>> From: James Green [mailto:james.mk.green@gmail.com]
>> Sent: Thursday, November 01, 2012 8:35 AM
>> To: users@activemq.apache.org
>> Subject: Re: Whitelisting forwarded queues
>>
>> Are you referring to this discussion, had only days ago?
>>
>> http://mail-archives.apache.org/mod_mbox/activemq-users/201210.mbox/%3CCAMH6+azsejiNB8zadd5_VYo0U_9Y-42Uyg+7YC6To7zt+k5Zxw@mail.gmail.com%3E
>>
>>
>> On 31 October 2012 23:45, Geurt Schimmel <GS...@schubergphilis.com>wrote:
>>
>>> BrokerA is forwarding a number of queues with
>>> <staticallyIncludedDestinations> to BrokerB.
>>> How can BrokerB prevent BrokerA from relentlessly forwarding whatever
>>> BrokerA likes (and only allow the queues to be forwarded that were
>>> agreed) using Spring XML ?
>>>
>>> Thanks.
>
>
>
> --
> http://redhat.com
> http://blog.garytully.com
Re: Whitelisting forwarded queues
Posted by Gary Tully <ga...@gmail.com>.
the default for a network bridge is to forward on demand, so when
there is a remote consumer. In this way, only destinations that have
remote consumers will get messages
forwarded.
with staticallyIncludedDestinations, you say, create a local consumer
for this destination and forward irrespective of demand. so always
forward.
So if you only want to have TEST.FOO forwarded because that is the
only destination that has consumers on it, using the default demand
forwarding will work fine.
On 1 November 2012 10:29, Geurt Schimmel <GS...@schubergphilis.com> wrote:
> No, this is another issue I think.
> When I configure my broker to forward ">" to you, and you only expect and process the queue "TEST.FOO", it might get messy on your broker (in the best case with a few messages to a few queues, in the worst case, your broker will become unresponsive). Sure, if you are aware of the unsolicited forwarding the network-traffic has already occurred, but you want to keep your broker alive and clean. So I'm looking for a solution for that problem.
>
> Geurt
>
> -----Original Message-----
> From: James Green [mailto:james.mk.green@gmail.com]
> Sent: Thursday, November 01, 2012 8:35 AM
> To: users@activemq.apache.org
> Subject: Re: Whitelisting forwarded queues
>
> Are you referring to this discussion, had only days ago?
>
> http://mail-archives.apache.org/mod_mbox/activemq-users/201210.mbox/%3CCAMH6+azsejiNB8zadd5_VYo0U_9Y-42Uyg+7YC6To7zt+k5Zxw@mail.gmail.com%3E
>
>
> On 31 October 2012 23:45, Geurt Schimmel <GS...@schubergphilis.com>wrote:
>
>> BrokerA is forwarding a number of queues with
>> <staticallyIncludedDestinations> to BrokerB.
>> How can BrokerB prevent BrokerA from relentlessly forwarding whatever
>> BrokerA likes (and only allow the queues to be forwarded that were
>> agreed) using Spring XML ?
>>
>> Thanks.
>>
>>
--
http://redhat.com
http://blog.garytully.com
RE: Whitelisting forwarded queues
Posted by Geurt Schimmel <GS...@schubergphilis.com>.
No, this is another issue I think.
When I configure my broker to forward ">" to you, and you only expect and process the queue "TEST.FOO", it might get messy on your broker (in the best case with a few messages to a few queues, in the worst case, your broker will become unresponsive). Sure, if you are aware of the unsolicited forwarding the network-traffic has already occurred, but you want to keep your broker alive and clean. So I'm looking for a solution for that problem.
Geurt
-----Original Message-----
From: James Green [mailto:james.mk.green@gmail.com]
Sent: Thursday, November 01, 2012 8:35 AM
To: users@activemq.apache.org
Subject: Re: Whitelisting forwarded queues
Are you referring to this discussion, had only days ago?
http://mail-archives.apache.org/mod_mbox/activemq-users/201210.mbox/%3CCAMH6+azsejiNB8zadd5_VYo0U_9Y-42Uyg+7YC6To7zt+k5Zxw@mail.gmail.com%3E
On 31 October 2012 23:45, Geurt Schimmel <GS...@schubergphilis.com>wrote:
> BrokerA is forwarding a number of queues with
> <staticallyIncludedDestinations> to BrokerB.
> How can BrokerB prevent BrokerA from relentlessly forwarding whatever
> BrokerA likes (and only allow the queues to be forwarded that were
> agreed) using Spring XML ?
>
> Thanks.
>
>
Re: Whitelisting forwarded queues
Posted by James Green <ja...@gmail.com>.
Are you referring to this discussion, had only days ago?
http://mail-archives.apache.org/mod_mbox/activemq-users/201210.mbox/%3CCAMH6+azsejiNB8zadd5_VYo0U_9Y-42Uyg+7YC6To7zt+k5Zxw@mail.gmail.com%3E
On 31 October 2012 23:45, Geurt Schimmel <GS...@schubergphilis.com>wrote:
> BrokerA is forwarding a number of queues with
> <staticallyIncludedDestinations> to BrokerB.
> How can BrokerB prevent BrokerA from relentlessly forwarding whatever
> BrokerA likes (and only allow the queues to be forwarded that were agreed)
> using Spring XML ?
>
> Thanks.
>
>