[jira] [Comment Edited] (AMQ-5997) MQTT legacy client support

["Dejan Bosanac (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943232#comment-14943232 ] 

Dejan Bosanac edited comment on AMQ-5997 at 10/5/15 11:08 AM:
--------------------------------------------------------------

Fixed mqtt client and released 1.12. Upgraded the broker and added a check on unsubscribe method to support this behaviour only if client is 3.1 and transport.publishDollarTopic=true (another legacy option) is also used.


was (Author: dejanb):
Fixed mqtt client and released 1.12. Upgraded the broker and added a check on unsubscribe method to support this behaviour only if client is 3.1 and transport.publishDollarTopic=true (another legacy option is still used).

> MQTT legacy client support
> --------------------------
>
>                 Key: AMQ-5997
>                 URL: https://issues.apache.org/jira/browse/AMQ-5997
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.12.0
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.13.0
>
>
> MQTT 3.1.1 spec defines that UNSUBSCRIBE packet needs to define AT_LEAST_ONCE (01) for fixed header QoS bits. But older clients might set those to some different value, like AT_MOST_ONCE. At the moment, the mqtt-client lib will try to have this case differently and we'll get 
> {code}ProtocolException: Invalid message encoding{code}
> error.
> The solution is to make mqtt client parse these other values regularly and introduce the necessary checks for 3.1.1 spec version in the broker.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)