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 <gschim...@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.gr...@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+k5...@mail.gmail.com%3E > > > On 31 October 2012 23:45, Geurt Schimmel <gschim...@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
