I saw that. Is there a way of doing this on the target? Our hub has no network connectors - they exist on the remote installs.
James On 15 August 2012 16:41, Dejan Bosanac <de...@nighttale.net> wrote: > Hi James, > > take a look at excludedDestinations property on network connectors. > You even have some examples here > > http://activemq.apache.org/networks-of-brokers.html > > > Regards > -- > Dejan Bosanac > Senior Software Engineer | FuseSource Corp. > dej...@fusesource.com | fusesource.com > skype: dejan.bosanac | twitter: @dejanb > blog: http://www.nighttale.net > ActiveMQ in Action: http://www.manning.com/snyder/ > > > On Wed, Aug 15, 2012 at 5:32 PM, James Green <james.mk.gr...@gmail.com> > wrote: > > Hi, > > > > We have three remote ActiveMQ installs each connecting to a central hub. > > > > Each remote ActiveMQ install creates queues dynamically, one per customer > > account, named "Outbound.Account.X". The customer can connect to their > > allocated installation. All works well. > > > > Trouble is, we have well over 1,000 queues showing on the central hub. > The > > hub never sends or receives of these queues. > > > > To save our hub machine's memory, can I tell the hub to ignore queues > named > > "Outbound.Account.X"? > > > > Thanks, > > > > James >
