[OASIS Issue Tracker] (MQTT-299) Metadata: CONNECT and CONNACK Maximum Message Length

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

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

Ed Briggs commented on MQTT-299:
--------------------------------

We now have added 'reason strings' which can accompany any of the acknowledgements, and any of these strings could exceed the maximum packet size, which means just about anything can break.

What I worry about is this.  Suppose you have 1 million clients, and a programming error results in an oversize message getting sent to them all (say somebody decides to serialize a 'network timeout' exception call stack into an 'reason string'. )  We *really* want to prevent 1 million clients going into a reconnect/retry cycle. 



> Metadata: CONNECT and CONNACK Maximum Message Length
> ----------------------------------------------------
>
>                 Key: MQTT-299
>                 URL: https://issues.oasis-open.org/browse/MQTT-299
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: 5
>            Reporter: Brian Raymor
>            Assignee: Ed Briggs
>
> This was discussed in MQTT-276 (with notes from the F2F meetings) and has been tracked in MQTT-256 (Metadata). 
> I'm opening a separate, specific issue per Ken's comments - https://issues.oasis-open.org/browse/MQTT-256?focusedCommentId=62192&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-62192:
> "All of these would be defined in separate JIRAs, but what we should do in this JIRA is to define the mechanism used to pass these values."



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