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

When the client's clean_session is set to false, after a normal disconnection, but the start_keep_alive_timer method is already running? #11

Open
fikersd opened this issue Sep 12, 2024 · 2 comments

Comments

@fikersd
Copy link

fikersd commented Sep 12, 2024

No description provided.

@TheWaWaR
Copy link
Contributor

Sounds like a long exists bug, will check this out.

@fikersd fikersd closed this as completed Sep 12, 2024
@fikersd fikersd reopened this Sep 13, 2024
@fikersd
Copy link
Author

fikersd commented Sep 13, 2024

start_keep_alive_timer running still works on the previous client ID.

New inner client ID are only generated here. When clean session is false, the previous client ID is reused. If the client does not publish a ping or other packet after going online, the client will be kicked.

new inner client id

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

No branches or pull requests

2 participants