[jira] [Commented] (ARTEMIS-2888) MQTT spec violation when subscribed to wildcard topic
[ https://issues.apache.org/jira/browse/ARTEMIS-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17216734#comment-17216734 ] ASF subversion and git services commented on ARTEMIS-2888: -- Commit 583bd3602a62af0b80676c7677d81affc80fe6ef in activemq-artemis's branch refs/heads/master from gtully [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=583bd36 ] ARTEMIS-2888 ARTEMIS-2859 ARTEMIS-2768 - revert new page-store-name addressSetting, when the page store respects the target address and the size is tallied on the target address store, it is no longer neecessary > MQTT spec violation when subscribed to wildcard topic > - > > Key: ARTEMIS-2888 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2888 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: MQTT >Affects Versions: 2.14.0 > 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 >Reporter: Florian Meister >Assignee: Gary Tully >Priority: Major > Fix For: 2.16.0 > > Attachments: image-2020-08-27-12-37-01-479.png > > Time Spent: 2h > Remaining Estimate: 0h > > 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 > !image-2020-08-27-12-37-01-479.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2888) MQTT spec violation when subscribed to wildcard topic
[ https://issues.apache.org/jira/browse/ARTEMIS-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17201389#comment-17201389 ] ASF subversion and git services commented on ARTEMIS-2888: -- Commit fa04881c6f6e44e4de8b2b70a0be181185d1e1ca in activemq-artemis's branch refs/heads/master from gtully [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=fa04881 ] ARTEMIS-2888 ARTEMIS-2859 ARTEMIS-2768 - new page-store-name addressSetting to allow wildcard subscriptions share a single page store > MQTT spec violation when subscribed to wildcard topic > - > > Key: ARTEMIS-2888 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2888 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: MQTT >Affects Versions: 2.14.0 > 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 >Reporter: Florian Meister >Assignee: Gary Tully >Priority: Major > Attachments: image-2020-08-27-12-37-01-479.png > > Time Spent: 1.5h > Remaining Estimate: 0h > > 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 > !image-2020-08-27-12-37-01-479.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2888) MQTT spec violation when subscribed to wildcard topic
[ https://issues.apache.org/jira/browse/ARTEMIS-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17201392#comment-17201392 ] ASF subversion and git services commented on ARTEMIS-2888: -- Commit 622acf1da1b6da3cc170cd4f5d8933f2fdce1467 in activemq-artemis's branch refs/heads/master from Gary Tully [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=622acf1 ] Merge pull request #3265 from gtully/ARTEMIS-2888 ARTEMIS-2888 ARTEMIS-2859 ARTEMIS-2768 - new page-store-name addressSetting to allow wildcard subscriptions share a single page store > MQTT spec violation when subscribed to wildcard topic > - > > Key: ARTEMIS-2888 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2888 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: MQTT >Affects Versions: 2.14.0 > 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 >Reporter: Florian Meister >Assignee: Gary Tully >Priority: Major > Attachments: image-2020-08-27-12-37-01-479.png > > Time Spent: 1.5h > Remaining Estimate: 0h > > 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 > !image-2020-08-27-12-37-01-479.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2888) MQTT spec violation when subscribed to wildcard topic
[ https://issues.apache.org/jira/browse/ARTEMIS-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17201393#comment-17201393 ] ASF subversion and git services commented on ARTEMIS-2888: -- Commit 622acf1da1b6da3cc170cd4f5d8933f2fdce1467 in activemq-artemis's branch refs/heads/master from Gary Tully [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=622acf1 ] Merge pull request #3265 from gtully/ARTEMIS-2888 ARTEMIS-2888 ARTEMIS-2859 ARTEMIS-2768 - new page-store-name addressSetting to allow wildcard subscriptions share a single page store > MQTT spec violation when subscribed to wildcard topic > - > > Key: ARTEMIS-2888 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2888 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: MQTT >Affects Versions: 2.14.0 > 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 >Reporter: Florian Meister >Assignee: Gary Tully >Priority: Major > Attachments: image-2020-08-27-12-37-01-479.png > > Time Spent: 1.5h > Remaining Estimate: 0h > > 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 > !image-2020-08-27-12-37-01-479.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2888) MQTT spec violation when subscribed to wildcard topic
[ https://issues.apache.org/jira/browse/ARTEMIS-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17200860#comment-17200860 ] Gary Tully commented on ARTEMIS-2888: - I have settled on 'page-store-name' to allow a page store to be shared by a hierarchy of addresses. This is necessary to avoid inconsistency in resource usage calculations. A subscription can only deal with a single page store at the moment, and if there is more than one in play it will compete to page and update counters etc.. leading to problems. A.shared If wildcard routing is in play, and addresses will page, then we need to explicitly indicate that page store that that hierarchy will use. Ie: this new address setting is mandatory in this situation. some more detail in the PR https://github.com/apache/activemq-artemis/pull/3265/files > MQTT spec violation when subscribed to wildcard topic > - > > Key: ARTEMIS-2888 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2888 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: MQTT >Affects Versions: 2.14.0 > 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 >Reporter: Florian Meister >Assignee: Gary Tully >Priority: Major > Attachments: image-2020-08-27-12-37-01-479.png > > Time Spent: 40m > Remaining Estimate: 0h > > 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 > !image-2020-08-27-12-37-01-479.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2888) MQTT spec violation when subscribed to wildcard topic
[
https://issues.apache.org/jira/browse/ARTEMIS-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17198279#comment-17198279
]
Gary Tully commented on ARTEMIS-2888:
-
maybe it should be
{code}
A.shared
{code}
> MQTT spec violation when subscribed to wildcard topic
> -
>
> Key: ARTEMIS-2888
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2888
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: MQTT
>Affects Versions: 2.14.0
> 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
>Reporter: Florian Meister
>Assignee: Gary Tully
>Priority: Major
> Attachments: image-2020-08-27-12-37-01-479.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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
> !image-2020-08-27-12-37-01-479.png!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2888) MQTT spec violation when subscribed to wildcard topic
[
https://issues.apache.org/jira/browse/ARTEMIS-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17198257#comment-17198257
]
Gary Tully commented on ARTEMIS-2888:
-
paging is at the root of this problem. The destination header is populated from
the address and the address field in a message is modified on write to paging.
Paging is being initiated by the subscription queues with the subscribe to
address, hense the wrong destination coming from the page store name.
A quick mod to not modify the address is the simplest solution, however I guess
this will break something else, hopefully the full test suite will uncover.
As it stands, If in understand this correctly, there are multiple copies of
messages in page-files for each subscription but it seems to hang together.
An better approach, to use less resources wold be to allow an address setting
to specify a pagingAddress (or page store name) that could be shared by address
hierarchies.
{code}
A.shared
{code}
In this way, subscribe to A.* and publish to A.a would use the same page store
named A.shared. In the absence of a non null page-store-name, the address will
be used as the store name as is the current default.
The downside to this sort of sharing will be the paging penalty is one consumer
is slow, in a similar way as selectors can fragment an address.
However for high volume addresses, where there are many consumers, avoiding
multiple copies of messages when paging will be preferable.
With this page store alias capability, the message address will still need to
be left intact, unless we find a better way to populate the destination header.
any better suggestion for ?
> MQTT spec violation when subscribed to wildcard topic
> -
>
> Key: ARTEMIS-2888
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2888
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: MQTT
>Affects Versions: 2.14.0
> 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
>Reporter: Florian Meister
>Assignee: Gary Tully
>Priority: Major
> Attachments: image-2020-08-27-12-37-01-479.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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
> !image-2020-08-27-12-37-01-479.png!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2888) MQTT spec violation when subscribed to wildcard topic
[
https://issues.apache.org/jira/browse/ARTEMIS-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17196961#comment-17196961
]
Florian Meister commented on ARTEMIS-2888:
--
# Create an anycast queue for +/bar.
{code:java}
{code}
# Set max-size and page-size to small values to force paging immediately
(optional)
{code:java}
100
10
PAGE
{code}
# Add a subscriber to +/bar with QOS 1.
# Add a publisher, frequently publishing messages with QOS 1.
# Disconnect the subscriber (not unsubscribe).
# Wait until Artemis starts paging for +/bar.
# Connect the subscriber again.
# Messages gets delivered which were queued previously
# Disconnect Subscriber
# Reconnect Subscriber
# Publish messages while subscribed
# When publishing while subscribed every 2nd message is sent with topic-filter
instead of topic name
{code:java}
root@tnetw0605:/etc/logstash/conf.d# mosquitto_sub -h mqtt.dev.smartprod.io -u
user -P password -i barsubscriber -t "+/bar" -v
514e4d21-2307-11e9-ad2f-005056b451d2/bar test
+/bar test
514e4d21-2307-11e9-ad2f-005056b451d2/bar test
+/bar test
514e4d21-2307-11e9-ad2f-005056b451d2/bar test
+/bar test
514e4d21-2307-11e9-ad2f-005056b451d2/bar test
+/bar test
514e4d21-2307-11e9-ad2f-005056b451d2/bar test
+/bar test
514e4d21-2307-11e9-ad2f-005056b451d2/bar test
+/bar test
514e4d21-2307-11e9-ad2f-005056b451d2/bar test
+/bar test
514e4d21-2307-11e9-ad2f-005056b451d2/bar test
+/bar test
{code}
# When subscribing after publishing some messages every message is delivered
with topic-filter instead of topic name
{code:java}
root@tnetw0605:/etc/logstash/conf.d# mosquitto_sub -h mqtt.dev.smartprod.io -u
user -P password -i barsubscriber -t "+/bar" -v
+/bar test
+/bar test
+/bar test
+/bar test
+/bar test
+/bar test
+/bar test
+/bar test
+/bar test
+/bar test
+/bar test
+/bar test
+/bar test
+/bar test
{code}
> MQTT spec violation when subscribed to wildcard topic
> -
>
> Key: ARTEMIS-2888
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2888
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: MQTT
>Affects Versions: 2.14.0
> 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
>Reporter: Florian Meister
>Priority: Major
> Attachments: image-2020-08-27-12-37-01-479.png
>
>
> 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
> !image-2020-08-27-12-37-01-479.png!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2888) MQTT spec violation when subscribed to wildcard topic
[
https://issues.apache.org/jira/browse/ARTEMIS-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17187565#comment-17187565
]
Florian Meister commented on ARTEMIS-2888:
--
Below the broker.xml. The only relevant change is global_max_size=100M and
defining the queue for address
"*.from-smart-acquisition-device.part-count.event" as anycast queue. This was
to check if the queue type is changing the behavior. it happens with multicast
too.
{code:java}
http://www.w3.org/2001/XMLSchema-instance;
xmlns:xi="http://www.w3.org/2001/XInclude;
xsi:schemaLocation="urn:activemq
/schema/artemis-configuration.xsd"> http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="urn:activemq:core ">
integrationbus-dev
true
ASYNCIO
data/paging
data/bindings
data/journal
data/large-messages
true
2
10
4096
10M
68000
4096
5000
90
true
12
6
HALT
3296000
100Mb
tcp://0.0.0.0:8883?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=MQTT;useEpoll=true
DLQ
ExpiryQueue
0
-1
10
PAGE
true
true
true
true
DLQ
ExpiryQueue
0
-1
10
PAGE
true
true
true
true
{code}
> MQTT spec violation when subscribed to wildcard topic
> -
>
> Key: ARTEMIS-2888
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2888
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: MQTT
>Affects Versions: 2.14.0
> 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
>Reporter: Florian Meister
>Priority: Major
> Attachments: image-2020-08-27-12-37-01-479.png
>
>
> 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
> !image-2020-08-27-12-37-01-479.png!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2888) MQTT spec violation when subscribed to wildcard topic
[
https://issues.apache.org/jira/browse/ARTEMIS-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17187562#comment-17187562
]
Florian Meister commented on ARTEMIS-2888:
--
Below you can find a trace of one specific MQTT Message. It is published by
"end_to_end_dev" and then gets forwarded to "b4b8135fd3d8446b8612d110d55b4afe"
- via an MQTT subscription. You can see that the topic artemis publishes the
message is including wildcards. It seems it uses the topic filter instead of
the topic name.
{code:java}
Aug 31 10:19:38 chsfslx0108 bash[1256]: 2020-08-31 10:19:38,266 TRACE
[org.apache.activemq.artemis.core.protocol.mqtt] MQTT(end_to_end_dev): IN <<
PUBLISH(597)
topic=8414493f-22a5-47af-a5f6-8ebfd63d51d7/from-smart-acquisition-device/part-count/event,
qos=AT_LEAST_ONCE, retain=false, dup=false,
payload={"timestamp":1598861978264,"deviceId":"8414493f-22a5-47af-a5f6-8ebfd63d51d7","partCountData":{"totalParts":592,"badParts":4,"timestamp":1598861978264}}
Aug 31 10:19:38 chsfslx0108 bash[1256]: 2020-08-31 10:19:38,274 TRACE
[org.apache.activemq.artemis.core.protocol.mqtt] MQTT(end_to_end_dev): OUT >>
PUBACK(597)
Aug 31 10:19:38 chsfslx0108 bash[1256]: 2020-08-31 10:19:38,274 TRACE
[org.apache.activemq.artemis.core.protocol.mqtt]
MQTT(b4b8135fd3d8446b8612d110d55b4afe): OUT >> PUBLISH(-2123119238)
topic=+/from-smart-acquisition-device/part-count/event, qos=AT_MOST_ONCE,
retain=false, dup=false,
payload={"timestamp":1598861978264,"deviceId":"8414493f-22a5-47af-a5f6-8ebfd63d51d7","partCountData":{"totalParts":592,"badParts":4,"timestamp":1598861978264}}
{code}
It seems this behaviour is only happening when the queue is in paging mode (or
when there are many messages in it). Currently there are sitting around 90M
Messages in it and the queue is in paging mode. Other topics/queues which are
not in paging mode are working normal.
Below a little bit more logs
{code:java}
Aug 31 10:19:39 chsfslx0108 bash[1256]: 2020-08-31 10:19:39,266 TRACE
[org.apache.activemq.artemis.core.protocol.mqtt] MQTT(end_to_end_dev): IN <<
PUBLISH(598)
topic=8414493f-22a5-47af-a5f6-8ebfd63d51d7/from-smart-acquisition-device/part-count/event,
qos=AT_LEAST_ONCE, retain=false, dup=false,
payload={"timestamp":1598861979264,"deviceId":"8414493f-22a5-47af-a5f6-8ebfd63d51d7","partCountData":{"totalParts":593,"badParts":4,"timestamp":1598861979264}}
Aug 31 10:19:39 chsfslx0108 bash[1256]: 2020-08-31 10:19:39,272 TRACE
[org.apache.activemq.artemis.core.protocol.mqtt] MQTT(end_to_end_dev): OUT >>
PUBACK(598)
Aug 31 10:19:39 chsfslx0108 bash[1256]: 2020-08-31 10:19:39,272 TRACE
[org.apache.activemq.artemis.core.protocol.mqtt]
MQTT(b4b8135fd3d8446b8612d110d55b4afe): OUT >> PUBLISH(-2123119233)
topic=+/from-smart-acquisition-device/part-count/event, qos=AT_MOST_ONCE,
retain=false, dup=false,
payload={"timestamp":1598861979264,"deviceId":"8414493f-22a5-47af-a5f6-8ebfd63d51d7","partCountData":{"totalParts":593,"badParts":4,"timestamp":1598861979264}}
Aug 31 10:19:40 chsfslx0108 bash[1256]: 2020-08-31 10:19:40,265 TRACE
[org.apache.activemq.artemis.core.protocol.mqtt] MQTT(end_to_end_dev): IN <<
PUBLISH(599)
topic=8414493f-22a5-47af-a5f6-8ebfd63d51d7/from-smart-acquisition-device/part-count/event,
qos=AT_LEAST_ONCE, retain=false, dup=false,
payload={"timestamp":1598861980264,"deviceId":"8414493f-22a5-47af-a5f6-8ebfd63d51d7","partCountData":{"totalParts":594,"badParts":4,"timestamp":1598861980264}}
Aug 31 10:19:40 chsfslx0108 bash[1256]: 2020-08-31 10:19:40,279 TRACE
[org.apache.activemq.artemis.core.protocol.mqtt] MQTT(end_to_end_dev): OUT >>
PUBACK(599)
Aug 31 10:19:40 chsfslx0108 bash[1256]: 2020-08-31 10:19:40,279 TRACE
[org.apache.activemq.artemis.core.protocol.mqtt]
MQTT(b4b8135fd3d8446b8612d110d55b4afe): OUT >> PUBLISH(-2123119229)
topic=+/from-smart-acquisition-device/part-count/event, qos=AT_MOST_ONCE,
retain=false, dup=false,
payload={"timestamp":1598861980264,"deviceId":"8414493f-22a5-47af-a5f6-8ebfd63d51d7","partCountData":{"totalParts":594,"badParts":4,"timestamp":1598861980264}}
Aug 31 10:19:41 chsfslx0108 bash[1256]: 2020-08-31 10:19:41,266 TRACE
[org.apache.activemq.artemis.core.protocol.mqtt] MQTT(end_to_end_dev): IN <<
PUBLISH(600)
topic=8414493f-22a5-47af-a5f6-8ebfd63d51d7/from-smart-acquisition-device/part-count/event,
qos=AT_LEAST_ONCE, retain=false, dup=false,
payload={"timestamp":1598861981264,"deviceId":"8414493f-22a5-47af-a5f6-8ebfd63d51d7","partCountData":{"totalParts":595,"badParts":4,"timestamp":1598861981264}}
Aug 31 10:19:41 chsfslx0108 bash[1256]: 2020-08-31 10:19:41,283 TRACE
[org.apache.activemq.artemis.core.protocol.mqtt] MQTT(end_to_end_dev): OUT >>
PUBACK(600)
Aug 31 10:19:41 chsfslx0108 bash[1256]: 2020-08-31 10:19:41,284 TRACE
[org.apache.activemq.artemis.core.protocol.mqtt]
MQTT(b4b8135fd3d8446b8612d110d55b4afe): OUT >> PUBLISH(-2123119225)
[jira] [Commented] (ARTEMIS-2888) MQTT spec violation when subscribed to wildcard topic
[ https://issues.apache.org/jira/browse/ARTEMIS-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17187501#comment-17187501 ] Florian Meister commented on ARTEMIS-2888: -- Hi Justin, thanks for the quick feedback. I did a bit troubleshooting on weekend and discovered that it does not occur when the queue is empty. I published a lot of messages (around 9M) without subscribers. Today I tried to subscribe with a new customer (new session) to the topic and voila - I get messages with the wildcard topic in it. Maybe it has something to do with paging? I'll get the logs for you now. > MQTT spec violation when subscribed to wildcard topic > - > > Key: ARTEMIS-2888 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2888 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: MQTT >Affects Versions: 2.14.0 > 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 >Reporter: Florian Meister >Priority: Major > Attachments: image-2020-08-27-12-37-01-479.png > > > 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 > !image-2020-08-27-12-37-01-479.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
