Exception raised when two MQTT client subscribes whith the same ClientID

I found an Exception raised when two MQTT client subscribes whith the same ClientID. The exception is raised in MqttPublisherManager.cs in method PublishThread() in the following line

var query = from p in this.retainedMessages where (new Regex(subscription.Topic)).IsMatch(p.Key) // check for topics based also on wildcard with regex select p.Value; Exception is raised because subscription.Topic is null. Each ClientID must be unique, but if it happens, this issue appears.

Regards

[dtflx01]

Hi, Yes I think that the Broker should refuse new connection. Regards

[nkostis]

As Vladimir says and as is common behaviour among brokers, the broker should allow the connection of the new client and disconnect the existing one, since they’re considered the same client that tries to reconnect and the previous connection is “stale”. This may lead to attacks (if client id is known to others), but the other option would be to have stale connections remain stale forever (keep-alive can be disabled by a client).

so the question actually is: what does the broker currently do and how do you get into a situation where there are more than one clients with the same ID connected? Because i use this broker as well and what i’ve seen it do is to indeed disconnect the original one. And since my clients have an auto-reconnect mechanism, you actually see one client kick the other one out and vice versa for eternity