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

XML

Word

Printable

JSON

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

Hide

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

Show
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

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:

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

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

Estimated:

Not Specified

Remaining:

Logged:

2h 20m