We are running a network of brokers, but I'm tracking down a memory issue and one of the "theories" is that messages sent to Advisory topics is not being freed because we see [sometimes very large] numbers of messages enqueued, no messages dequeued, and a non-zero number of consumers. Is that something that's possible?
On 9/21/15, 8:46 PM, "tbai...@gmail.com on behalf of Tim Bain" <tbai...@gmail.com on behalf of tb...@alumni.duke.edu> wrote: >This is the first search result when I Google for 'activemq advisory': >http://activemq.apache.org/advisory-message.html > >If you're not trying to explicitly use advisory topics yourself, you can >ignore them; brokers in a network of brokers use them to figure out where >consumers are, but you don't have to do anything with them. If you're not >running a network of brokers, you'll get a small performance boost by >turning them off, as described on the page I linked. Note that it's a >small benefit and that you'll have to remember to undo the change if you >ever move to a network of brokers topology; consider whether it's worth the >effort for your use case. > >On Mon, Sep 21, 2015 at 4:44 PM, Daniel Israel <disr...@liveops.com> wrote: > >> I see a large number of advisory topics (ActiveMQ.Advisory.*) in my list >> of topics, such as: >> >> ActiveMQ.Advisory.TempQueue >> >> >> What are these used for? Is it a problem if these Topics have consumers >> and none of the messages are dequeued? >> >> Thanks for any help. >>
smime.p7s
Description: S/MIME cryptographic signature
