Subscribe Client Timeout

[MiguelMar98]

Hello!

I have my publisher and subscriber clients successfully set up with AWS Iot Core. I can publish and subscribe to topics.

My publisher VI can run indefinitely if I keep publishing messages (I'm sending time stamp every 10 seconds). For this VI I left the Keep Alive field empty.

On the other hand, my subscriber VI keeps disconnecting after a while depending on the Keep Alive value I choose even though I keep receiving the timestamps sent by the publisher every 10 seconds. I added a ping VI after the event where I receive the published message and now it seems I can run without stopping (ran continuously for 1 hr).

My question is if this is the right way of keeping my subscriber connected to my broker or there is some other configuration at the connection that I am missing?

Thank you!

[francois-normandin]

Yes, that's somewhat expected if you use QoS =0. The server never received confirmation that you are sending any bytes, so it needs to be pinged at least once during the keep-alive time. I expect that a QoS>0 would act as a ping and keep connection source because you would be sending ACK packets back I would advise that you throttle the ping to every X seconds instead of pinging every time you receive a packet. That way, if you reuse the same pattern but with a much faster rate of incoming messages, you will not be pinging the server every 10ms or even faster.

…

________________________________ From: MiguelMar98 ***@***.***> Sent: Monday, April 8, 2024 3:21:02 PM To: LabVIEW-Open-Source/MQTT-Client ***@***.***> Cc: Subscribed ***@***.***> Subject: [LabVIEW-Open-Source/MQTT-Client] Subscribe Client Timeout (Issue #24) Hello! I have my publisher and subscriber clients successfully set up with AWS Iot Core. I can publish and subscribe to topics. My publisher VI can run indefinitely if I keep publishing messages (I'm sending time stamp every 10 seconds). For this VI I left the Keep Alive field empty. On the other hand, my subscriber VI keeps disconnecting after a while depending on the Keep Alive value I choose even though I keep receiving the timestamps sent by the publisher every 10 seconds. I added a ping VI after the event where I receive the published message and now it seems I can run without stopping (ran continuously for 1 hr). image.png (view on web)<https://github.com/LabVIEW-Open-Source/MQTT-Client/assets/166087050/7ddba0c3-fe71-4d62-b755-6f1533fcb600> My question is if this is the right way of keeping my subscriber connected to my broker or there is some other configuration at the connection that I am missing? Thank you! — Reply to this email directly, view it on GitHub<#24>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACZPNJARX2NHTXVCEHY7AVDY4MJ45AVCNFSM6AAAAABF5PNYKWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZTEMJZGUYDAOA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>