Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Client side delivery guarantee (QoS 1 or 2)
See original GitHub issueSteps:
1 - Connect to Broker 2 - Subscribe to the topic “test/” 2 - Disconnect the client 3 - Send a message to a topic “test/” with QoS 1 or 2 4 - Close the application 5 - Open the application 6 - Connect to Broker
Result:
Messages sent with QoS 1 and 2 will be lost
Expected results
Resend messages after restarting the application using MQTT only
By MQTT protocol specification, when using QoS 1 or 2, you are guaranteed that the message arrives in the broker, but if the client is offline and restart the application, the message will be loss
Using ManagedClient I will have the guarantee that the message will be delivered, but it has some limitations like CleanSession = false, so I can not guarantee that QoS 1 or 2 will reach me
It seems to me that the QoS 1 and 2 delivery guarantee defined in the MQTT protocol is not being met.
Is there any plan for this?
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ah that was a mistake. This feature will be added as soon as there is time for it. As long as this is not implemented I recommend to use the regular client and doing the storage of the application messages manually.
What’s the status of this @chkr1011?