Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QOS 1 together with retained messages can lead to looping reconnect cycle (MQTT 5.0) #594

Open
joggeli34 opened this issue Sep 6, 2023 · 0 comments
Labels

Comments

@joggeli34
Copy link

🐛 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):

  1. Retained message is received
  2. A same message is received as duplicate as it must be resent when it wasn't acknowledged in the former connection.
  3. The connection is closed, same starts again

🔬 How To Reproduce

Steps to reproduce the behavior:

  1. Use QoS 1 with retained messages
  2. 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

@joggeli34 joggeli34 added the bug label Sep 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant