[OASIS Issue Tracker] (MQTT-262) Clarify will messages if server disconnects

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/MQTT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59273#comment-59273 ] 

Andrew Banks commented on MQTT-262:
-----------------------------------

Ken, I agree, receipt of DISCONNECT removes the will message, any other disconnection causes it to be published. The relevant section of the specification is:

3.1.2.5 Will Flag

Position: bit 2 of the Connect Flags.

If the Will Flag is set to 1 this indicates that, if the Connect request is accepted, a Will Message MUST be stored on the Server and associated with the Network Connection. The Will Message MUST be published when the Network Connection is subsequently closed unless the Will Message has been deleted by the Server on receipt of a DISCONNECT Packet [MQTT-3.1.2-8].

Situations in which the Will Message is published include, but are not limited to:
An I/O error or network failure detected by the Server.
The Client fails to communicate within the Keep Alive time.
The Client closes the Network Connection without first sending a DISCONNECT Packet.
The Server closes the Network Connection because of a protocol error.
 

> Clarify will messages if server disconnects
> -------------------------------------------
>
>                 Key: MQTT-262
>                 URL: https://issues.oasis-open.org/browse/MQTT-262
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: futures
>    Affects Versions: 3.1.1
>            Reporter: Raphael Cohen
>            Assignee: Raphael Cohen
>
> If a server disconnects a connection because a second client has connected with the same client id, should the first connections' will message be sent? I would argue it should, because this scenario is intended to reflect 'stuck' and 'hung' clients.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)