[OASIS Issue Tracker] Commented: (MQTT-35) What is supposed to happen when the KeepAlive timeout expires?

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

    [ http://tools.oasis-open.org/issues/browse/MQTT-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33877#action_33877 ] 

Nick O'Leary commented on MQTT-35:
----------------------------------

Agreed that a keep-alive expiry should be the same as a network failure - that was always the intent.

As for the statement about not impacting the client's subscriptions - agreed that needs to either be removed, or qualified in terms of cleanSession

> What is supposed to happen when the KeepAlive timeout expires?
> --------------------------------------------------------------
>
>                 Key: MQTT-35
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-35
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>            Reporter: Peter Niblett
>
> 1. Is a Will Message published on behalf of the client (assuming one was specified on the CONNECT)?
> I had always assumes that the answer to this is Yes, however WD04 lines 650-653 say
> "If the server does not receive a message from the client.... it disconnects the client as if the client had sent a DISCONNECT message". Now if the client sends a DISCONNECT message then a Will Message is not generated, so that would suggest one isn't generated in the keepAlive disconnect case either.
> 2.  The paragraph then goes on to say "This action does not impact any of the client's subscriptions".  This contradicts the discussion of cleanSession in 3.1.2.5.  According to that section the subscriptions are only unaffected if the client had connected using cleanSession = 0.  If it had used cleanSession = 1, then the subscriptions are deleted when a disconnect (of any kind) occurs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira