Please guide me where the KeepAliveTimeout server check is implemented #91
Replies: 6 comments
-
server starts keep-alive here you can override keep-alive period in handshake service |
Beta Was this translation helpful? Give feedback.
-
I see it is implemented here: |
Beta Was this translation helpful? Give feedback.
-
ntex-io has nothing to do with mqtt, you have to provide right timeout |
Beta Was this translation helpful? Give feedback.
-
I've read the explanation here: https://www.hivemq.com/blog/mqtt-essentials-part-10-alive-client-take-over/#:~:text=It%20is%20the%20responsibility%20of%20the%20MQTT%20client%20to%20set,to%20its%20current%20signal%20strength. |
Beta Was this translation helpful? Give feedback.
-
HandshakeAck::idle_timeout represents timeout fir server |
Beta Was this translation helpful? Give feedback.
-
Thank you, @fafhrd91, it seems it becomes clear to me. |
Beta Was this translation helpful? Give feedback.
-
According to MQTT spec:
It is the responsibility of the Client to ensure that the interval between Control Packets being sent does not exceed the Keep Alive value. In the absence of sending any other Control Packets, the Client MUST send a PINGREQ Packet [MQTT-3.1.2-23].
If the Keep Alive value is non-zero and the Server does not receive a Control Packet from the Client within one and a half times the Keep Alive time period, it MUST disconnect the Network Connection to the Client as if the network had failed [MQTT-3.1.2-24].
I'm interested in
one and a half time the Keep Alive time period
part. So for 30 seconds by default the server should wait for 45 seconds. Is that actually so?Beta Was this translation helpful? Give feedback.
All reactions