Thanks. Yes, we do have schedulePeriodForDestinationPurge set.
On Thursday, 18 May 2017 13:50:11 UTC+1, Charlie Sharpsteen wrote:
>
> In addition to the policyEntries, you'll also need to set
> schedulePeriodForDestinationPurge on the top-level element ---
> otherwise no GC sweeps will occur
In addition to the policyEntries, you'll also need to set
schedulePeriodForDestinationPurge on the top-level element ---
otherwise no GC sweeps will occur to clean the inactive queues out. For
example:
http://activemq.apache.org/schema/core; persistent="false"
Thank you very much for all the suggestions!
@Christopher Wood, Thanks, you've given us a few things there we can try.
We'll also try restarting just the hub next time there is a problem since
that will hopefully save a lot of time to get the system back up and
running.
@R.I. Pienaar, thanks.
Hello,
Do you have Reply Queue Pruning enabled?
I had the same problem until I configured this. Hope this helps.
MCollective sends replies on uniquely-named, single-use queues with names
like mcollective.reply.. These have to be deleted after about
five minutes, lest they clog up ActiveMQ’s
