activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <>
Subject Re: Saving bandwith in a network-of-brokers with lots of brokers via WAN
Date Thu, 30 Jun 2011 11:09:23 GMT
CACHE_CONSUMER will help, but also setting the networkConnector attribute
destinationFilter and if you don't want to bridge temp destinations
set bridgeTempDestinations="false"
It defaults to ">" so the network connector gets consumer advisories
for all destinations, but ideally it should be correlated (or
automatically determined) with the set of

<networkConnector uri="static:(...)" bridgeTempDestinations="false"
destinationFilter="Queue.A,ActiveMQ.Advisory.Consumer.Queue.B" >
       <queue physicalName="A"/>
       <queue physicalName="B"/>

The syntax for 'destinationFilter' is a little odd bc the value is
prefexed with "ActiveMQ.Advisory.Consumer." when it is applied.

I have created an enhancement to make this automatic.

The other alternative is to disable advisories and configure an
entirely static network topology using static includes, but messages
will flow independent of demand in that scenario.

On 30 June 2011 11:30, Martin C. <> wrote:
> Hi,
> we plan a setup with lots of remote sites, each of them having their
> own broker which are then connected via a network-of-brokers via a
> duplex connector. We'd like to use dynamicallyIncludedDestinations,
> but even in our small test installation we already see huge amounts of
> advisory messages. This is expected, as I understand that this is used
> for handling the dynamic includes. As we are using Spring's
> MessageListenerContainer, with a a lot of dynamic scaling to the
> current on-site load, a lot of Advisories are generated and already
> dominate the network traffic by far.
> Are there any options we can set in order to reduce the number of
> advisories? We are already using conduitSubscriptions=true so there'd
> be no need to go over-the-wire as long as there is at least a single
> consumer. I tried to exclude with
>  <topic physicalName="ActiveMQ.Advisory.>" />
> but this didn't result in any reduction of the messages sent via the
> network bridges.
> We are now evaluating if we can use CACHE_CONSUMER with the message
> listener container in order to reduce the number of subscription
> changes, but still there is a lot of noise due to number of consumers
> scaling up/down.
> Thanks for any hint!
> Best regards,
> Martin


View raw message