[
https://issues.apache.org/jira/browse/AMQ-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521513#comment-14521513
]
Dejan Bosanac edited comment on AMQ-5734 at 4/30/15 1:52 PM:
-------------------------------------------------------------
Hi Gary, yes this is expected behaviour.
{quote}A PUBLISH Packet with a RETAIN flag set to 1 and a payload containing
zero bytes will be processed as normal by the Server and sent to Clients with a
subscription matching the topic name. Additionally any existing retained
message with the same topic name MUST be removed and any future subscribers for
the topic will not receive a retained message {quote}
Thanks for fixing the test.
was (Author: dejanb):
Hi Gary, yes this is expected behavior.
{quote}A PUBLISH Packet with a RETAIN flag set to 1 and a payload containing
zero bytes will be processed as normal by the Server and sent to Clients with a
subscription matching the topic name. Additionally any existing retained
message with the same topic name MUST be removed and any future subscribers for
the topic will not receive a retained message {quote}
Thanks for fixing the test.
> Support MQTT 3.1 silent subscription fail
> -----------------------------------------
>
> Key: AMQ-5734
> URL: https://issues.apache.org/jira/browse/AMQ-5734
> Project: ActiveMQ
> Issue Type: Improvement
> Components: MQTT
> Affects Versions: 5.11.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.12.0
>
>
> There's a difference in what 3.1 and 3.1.1 specs say should happen when an
> unauthorised subscribe happens. In 3.1, the broker don't informs the client
> so it just silently ignores the problem. In 3.1.1 it sends special QoS back.
> We currently only implement the later. We need to implement also 3.1
> behaviour for older clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
