[ARTEMIS-2888] MQTT spec violation when subscribed to wildcard topic

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.14.0
• Fix Version/s: 2.16.0
• Component/s: MQTT

Environment

Message Producer:

MQTTnet Client

published Message to  0e5ed50e-ccea-4a42-8c3e-db0e2780222b/from-smart-acquisition-device/machine-state/event/off

 

Message Consumer:

MQTT Paho Java Client, also tested with HiveMQ Java Client.

Subscribed to +/from-smart-acquisition-device/machine-state/event/off

• Assignee: Gary Tully
• Reporter: Florian Meister
• Created: 27/Aug/20 10:43
• Updated: 06/Apr/21 22:58
• Resolved: 24/Sep/20 09:21

Description

Sometimes the topic name of published messages contains the topic filter instead of the topic name.

This is neither correct nor allowed in the MQTT 3.1.1 specification:

http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html#_Toc398718106

 

Below a screenshot of an example MQTT Packet sent from the Artemis Broker

 

Issue Links

• incorporates: ARTEMIS-2768 Negative AddressSize in JMX
• is fixed by: ARTEMIS-2859 Strange Address Sizes on clustered topics.
• is related to: ARTEMIS-3223 MQTT spec violation when subscribed to wildcard topic on redistribution
• links to: GitHub Pull Request #3265
• links to: GitHub Pull Request #3306