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.

Sign up for GitHub

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

Jump to bottom

Race condition when callingAblyRealtime#connect() on terminated state #1041

Closed
ttypic opened this issue Oct 14, 2024 · 0 comments · Fixed by #1042
Closed

Race condition when callingAblyRealtime#connect() on terminated state #1041

ttypic opened this issue Oct 14, 2024 · 0 comments · Fixed by #1042
Assignees
@ttypic
Labels
bug Something isn't working. It's clear that this does need to be fixed.

Comments

@ttypic
Copy link
Contributor

ttypic commented Oct 14, 2024 •
edited by sync-by-unito bot
Loading

There is a race condition during connection termination in the ConnectionManager. If connect() is called shortly after the connection is terminated, a new connection is not created because the old one still exists.

┆Issue is synchronized with this Jira Task by Unito
@ttypic ttypic added the bug Something isn't working. It's clear that this does need to be fixed. label Oct 14, 2024
@ttypic ttypic mentioned this issue Oct 14, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ttypic ttypic

Labels
bug Something isn't working. It's clear that this does need to be fixed.
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[ECO-5033] fix: race condition when callingAblyRealtime#connect() on terminated state ably/ably-java
1 participant
@ttypic