[ https://issues.oasis-open.org/browse/MQTT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59242#comment-59242 ]
Raphael Cohen commented on MQTT-262:
------------------------------------
If you have clients configured with duplicate client ids, then there's not much we can do until we add an explicit server-initiated DISCONNECT. Adding a server-generated client id will also help. Regardless, I'd still advocate this behaviour. Having clients with duplicate ids is a serious misconfiguration, and isn't a scenario it's reasonable to expect a broker to detect under normal operation. It is possible, but with scaled out brokers, it's fiendishly difficult.
> 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)
