You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The client closes the connection if a resend message is received during the same connection, which is fine. But when this message is a retained message, following will happen (together with emqx):
Retained message is received
A same message is received as duplicate as it must be resent when it wasn't acknowledged in the former connection.
The connection is closed, same starts again
🔬 How To Reproduce
Steps to reproduce the behavior:
Use QoS 1 with retained messages
Close the connection before ack
Environment
What version of this client are you using?
1.3.2
JVM version?
17
Which MQTT protocol version is being used?
MQTT 5.0
Which MQTT broker (name and version)?
Emqx 5.1.6
📈 Expected behavior
Duplicates of retained messages should be ignored at least once
The text was updated successfully, but these errors were encountered:
🐛 Bug Report
The client closes the connection if a resend message is received during the same connection, which is fine. But when this message is a retained message, following will happen (together with emqx):
🔬 How To Reproduce
Steps to reproduce the behavior:
Environment
What version of this client are you using?
1.3.2
JVM version?
17
Which MQTT protocol version is being used?
MQTT 5.0
Which MQTT broker (name and version)?
Emqx 5.1.6
📈 Expected behavior
Duplicates of retained messages should be ignored at least once
The text was updated successfully, but these errors were encountered: