-
Type: Task
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: MQTT-SN
-
Labels:None
Because in MQTT-SN we don't have a network connection, and packets can get reordered or not delivered, it's possible that a CONNACK in response to a CONNECT is never received. Then the client will try another CONNECT. If the server or transport layer is slow, then the CONNACK received by the endpoint sending the CONNECT, could be in response to the first CONNECT.
This is a problem if the data in the second CONNECT is different from that in the first - the client and server will have a virtual connection to each other, but potentially with different session information at each end.