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

Queueing for clean session/expired session #288

Closed
SgtSilvio opened this issue Jun 7, 2019 · 1 comment · Fixed by #398
Closed

Queueing for clean session/expired session #288

SgtSilvio opened this issue Jun 7, 2019 · 1 comment · Fixed by #398
Assignees
Milestone

Comments

@SgtSilvio
Copy link
Member

SgtSilvio commented Jun 7, 2019

Currently messages are only queued when the client has a session.
Reason: the pending messages must only be resent if the client has a session (MQTT spec, needed for QoS 2 guarantee), so resending queued messages in case of no session does not make a lot of sense, as the user does not really know if the message was already sent or is queued.

@SgtSilvio SgtSilvio changed the title Queueing for clean session/session expiry interval=0 Queueing for clean session/expired session Aug 6, 2019
@SgtSilvio SgtSilvio added this to the 1.2 milestone Apr 20, 2020
@SgtSilvio
Copy link
Member Author

With version 1.2 it is possible to set Reconnector.republishIfSessionExpired(true) In a DisconnectedListener. By default this setting is false.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant