[ARTEMIS-3180] Consumers with wildcards addresses broken

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.17.0
• Fix Version/s: 2.18.0
• Component/s: AMQP, Broker

Environment

Artemis 2.17.0

openjdk version "1.8.0_275"
OpenJDK Runtime Environment (build 1.8.0_275-b01)
OpenJDK 64-Bit Server VM (build 25.275-b01, mixed mode)

• Assignee: Gary Tully
• Reporter: Sebastian T
• Created: 12/Mar/21 16:18
• Updated: 09/Aug/21 17:57
• Resolved: 18/Mar/21 11:34

Description

While upgrading from Artemis 2.16.0 to 2.17.0 several of our test cases started failing.

We are using AMQP and QPid JMS to communicate to Artemis.

The issue seems to be related to subscriptions with wildcards.

Sending a message to an address "topics.aaa.bbb.ccc" with a consumer subscribed to "topics.#.aaa.#" and one with "topics.#.bbb.#" only the consumer subscribed to "topics.#.aaa.#" receives the message.

I am attaching a test case illustrating the issue.

Running "mvn test" executes it with Artemis 2.17.0 and will fail. "mvn test -Dartemis.version=2.16.0" executes the test with Artemis 2.16.0 and will succeed.

Issue Links

• is broken by: ARTEMIS-3033 use a structured tree with visitors for wildcard addresses to avoid duplicate cross linking in address impl
• is related to: ARTEMIS-1890 # any-word wildcard doesn't match zero words if not used at the end of a wildcard expression
• links to: GitHub Pull Request #3492