[jira] [Commented] (AMQ-6345) [MQTT] ping response without CONNECT

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on AMQ-6345:
------------------------------------------------------

Commit 6dacef1c9552edbad656c31d784179c2cd179b2e in activemq's branch refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=6dacef1 ]

https://issues.apache.org/jira/browse/AMQ-6345

The MQTT transport will now throw an exception if a PINGREQ is sent to
the broker if a CONNECT packet has not been received first as the spec
says CONNECT must be the first packet sent.


> [MQTT] ping response without CONNECT
> ------------------------------------
>
>                 Key: AMQ-6345
>                 URL: https://issues.apache.org/jira/browse/AMQ-6345
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: MQTT
>    Affects Versions: 5.13.3
>         Environment: Ubuntu Linux 14.04 
>            Reporter: Martin Tappler
>            Assignee: Christopher L. Shannon
>            Priority: Minor
>
> I am currently investigating the behavior of several MQTT brokers and noticed that the ActiveMQ broker responds to PINGREQ packets with PINGRESP packets even if no CONNECT packet has been sent before. 
> This would be a violation of MQTT-3.1.0-1 and MQTT-4.8.0-1 of MQTT v3.1.1 while MQTT v3.1 is not that strict about this issue, but does also state "When a TCP/IP socket connection is established from a client to a server, a protocol level session must be created using a CONNECT flow." (http://public.dhe.ibm.com/software/dw/webservices/ws-mqtt/mqtt-v3r1.html#connect)
> Since ActiveMQ supports MQTT v3.1 according to http://activemq.apache.org/,
> but also MQTT v3.1.1 according to Issue AMQ-4990, I am not sure whether this should actually be considered a bug. 



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