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
signature.asc
Description: This is a digitally signed message part.
