activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Burton <>
Subject Re: Destination garbage collection on network of brokers
Date Fri, 24 Apr 2015 06:11:37 GMT
GC should definitely work.. do they topics have consumers? If they have ANY
consumers this will block GC and they won’t be able to be reclaimed.

Also, the time is reset for each new consumer.

Another note.  If you have a LARGE number of topics that need to be GCd,
there’s a bug whereby ActiveMQ locks the entire broker during GC. It takes
about 200ms to reclaim a queue so if you have 50 topics that need go be GCd
you’re going to have a locked broker for 10s.

I have a patch for this so if you hit it I’ll try to get it published.

It’s actually in in git but it hasn’t been merged yet.

On Thu, Apr 23, 2015 at 7:40 AM, jack atwork <> wrote:

> Hi,
> I'm running a network of brokers (activemq 5.9.1) with a continuous flow of
> unique short lived topics.
> I'm configuring the policyEntry with gcInactiveDestinations="true" but it
> looks like these destinations are not being garbage collected even though
> they have no regular consumers as I'm seeing the number of topic threads
> rise continuously over the lifetime of the app.
> Having a poke around in the code I can see another property which is not
> documented 'gcWithNetworkConsumers'. It looks like without this set to true
> the consumers from the cluster will be treated as regular consumers and
> keep the destination active.
> Am I correct in thinking I need to set gcWithNetworkConsumers=true to
> enable gc?
> Thanks,
> Jack


Location: *San Francisco, CA*
… or check out my Google+ profile

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message