[
https://issues.apache.org/jira/browse/AMQ-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366552#comment-15366552
]
ASF subversion and git services commented on AMQ-6345:
------------------------------------------------------
Commit 7342b3760f4cc16c50f7477db13fdf4a48ddfc47 in activemq's branch
refs/heads/activemq-5.13.x from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=7342b37 ]
https://issues.apache.org/jira/browse/AMQ-6345
disabling failed assertion for test as it is expected based on how this
test is usin the client
(cherry picked from commit 667ea7c640dd0203b2ecdc83f74435e77cbe44ab)
> [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
> Fix For: 5.14.0, 5.13.4
>
>
> 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)
