activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (AMQ-6345) [MQTT] ping response without CONNECT
Date Thu, 07 Jul 2016 13:56:11 GMT


ASF subversion and git services commented on AMQ-6345:

Commit bad922c9ef4ffc9c6de03e4e5fd40e93342eb7f9 in activemq's branch refs/heads/activemq-5.13.x
from [~cshannon]
[;h=bad922c ]

Moving PINGREQ tests into its own test class so they aren't run more
than once

(cherry picked from commit b5b087d5585b734d15873303b1f35c572cafbe68)

> [MQTT] ping response without CONNECT
> ------------------------------------
>                 Key: AMQ-6345
>                 URL:
>             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." (
> Since ActiveMQ supports MQTT v3.1 according to,
> 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

View raw message