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

Retry timer is improperly cleared, causing it to fail to start the second time #898

Closed
Peter-Maguire opened this issue Feb 24, 2022 · 0 comments · Fixed by #899
Closed
Assignees
Labels
bug Something isn't working. It's clear that this does need to be fixed.

Comments

@Peter-Maguire
Copy link
Contributor

Peter-Maguire commented Feb 24, 2022

cancelRetryTimer clears the timeout but incorrectly sets suspendTimer to null instead of retryTimer, so the second time that the retry timer is called (if the connection is lost, regained, then lost again) it will not start, meaning that the channel will not try to re-attach

┆Issue is synchronized with this Jira Bug by Unito

@Peter-Maguire Peter-Maguire added the bug Something isn't working. It's clear that this does need to be fixed. label Feb 24, 2022
@Peter-Maguire Peter-Maguire self-assigned this Feb 24, 2022
Peter-Maguire pushed a commit that referenced this issue Feb 24, 2022
fix retry timer setting wrong variable to null (Fixes #898)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working. It's clear that this does need to be fixed.
Development

Successfully merging a pull request may close this issue.

1 participant