This looks like a bug. Go ahead and create a Jira and attach your
reproducer. Thanks!
Justin
On Mon, Mar 8, 2021 at 4:30 AM Thorsten Meinl
wrote:
> So I did some debugging and I believe I have found a bug in Artemis.
> I create two topics, "t.*" and "t.123" (all using JMS). I register two
> co
So I did some debugging and I believe I have found a bug in Artemis.
I create two topics, "t.*" and "t.123" (all using JMS). I register two
consumers on both "t.*" and "t.123" and send a message to "t.123". If the
consumers close both topics are correctly deleted from the broker. However, if
I d
I don't know if there's a way to see why it wasn't deleted from the web
console. You could always attach a debugger to the broker and inspect it
that way. I believe the two main classes involved here would be
org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl.AddressQueueReaper
and org
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 wi
First off, what version of ActiveMQ Artemis are you using?
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.
I think using a single topic
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 o
