Hi, Am Freitag, 5. März 2021, 17:35:32 CET schrieb Justin Bertram: > First off, what version of ActiveMQ Artemis are you using? Sorry, forgot to mention: 2.16.0
> Do you have auto-delete-addresses = true? If so, addresses *should* be > deleted automatically when they have no more bindings. The wildcard itself > is a binding so that's probably why the address isn't removed. Yes, auto-delete-addresses = true. During operation I can see the wilcard adress "jobs.\*" which *does* get auto-deleted after all consumers are gone. Also some other addresses (without wilcard consumers attached) get deleted but not the jobs.A, jobs.B, ... addresses. Is there a way to see why they would stay there? In the "Attributes" tab in the Artemis Console I can see "Address size", "All queue names" and "Binding names" and all three are 0 or empty. > I think using a single topic with selectors on the subscriptions is a > viable alternative. There shouldn't be any performance penalty and the > semantics should be exactly what you're looking for. OK, good to hear. The we may likely go that way. Thanks! Thorsten > On Fri, Mar 5, 2021 at 10:09 AM Thorsten Meinl <thorsten.me...@knime.com> > > wrote: > > Hi, > > > > We are currently building an application using ActiveMQ Artemis. The rough > > setup is as follows: We have consumers that are interested in all messages > > and > > other consumers that are only interested in a subset. So far we have been > > using topic hierarchies. The first group of consumers listens on e.g. > > "jobs.*" > > whereas the others listens on "jobs.A", "jobs.B", etc. All addresses, > > topics, > > queues are auto-created. What we notice now is that even if all consumers > > are > > gone there are still addresses "jobs.A", "jobs.B", ... remaining even > > though > > they don't have anything attached to them any more. No consumers, no > > queues, > > nothing. Therefore the first question: why is this and how can we prevent > > it? > > > > An alternative approach would be to use just one topic "jobs" and filter > > messages with message selectors (e.g. "id=A", "id=B", ...). This would > > eliminate the issue above. The question is whether there is a performance > > or > > functionality penalty involved with this approach. > > > > Thanks, > > > > Thorsten > > > > -- > > Dr.-Ing. Thorsten Meinl > > KNIME AG > > Hardturmstrasse 66 > > 8005 Zurich, Switzerland -- Dr.-Ing. Thorsten Meinl KNIME AG Hardturmstrasse 66 8005 Zurich, Switzerland
signature.asc
Description: This is a digitally signed message part.
