There is an issue when we have the following setup:

• Shared durable consumer A listening to news.#
• Shared durable consumer B listening to news.europe.#
• Message M1 sent to news.europe.sports
• Message M2 sent to news.europe

Expected behavior:

• A receives M1 and M2
• B receives M1 and M2

Actual behavior:

• A receives M1 and M2
• B receives M1

This happens when it is run with a clean Artemis, i.e. without any previous data. If we run it a second time B receives M1 and M2. When using consumer.receive() it also works as expected.

This also affects at least version 3.0.0-SNAPSHOT however I couldn't select it so I chose the second version I've tested it for. The attached project showcases the bug where I simply adjusted the example apache-artemis-3.0.0-SNAPSHOT/examples/features/standard/topic-hierarchies.

I couldn't test it with 2.29.0-SNAPSHOT since I would get exceptions concerning the topic not being multicast (already with the original example).