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

Websocket Blocks after terminating without unsubscribing #1

Closed
samuel-tay opened this issue Nov 8, 2021 · 2 comments
Closed

Websocket Blocks after terminating without unsubscribing #1

samuel-tay opened this issue Nov 8, 2021 · 2 comments

Comments

@samuel-tay
Copy link

As discussed on Discord https://discord.com/channels/783264383978569728/783264902613565450/907267013028749322

It was discovered that subscribing to WS works.

However, if a subscription is not unsubscribed and the session is terminated, then the WS blocks up and no further requests will be entertained. It doesn't help to reconnect and unsubscribe.

Also, in the instance where 2 clients are connected and if Client A terminates the session without unsubscribing, Client B blocks as well, and the whole WS blocks.

@samuel-tay
Copy link
Author

@xfwil
Copy link

xfwil commented Nov 8, 2021

I had same with this issue too, i hope this can fix fastly. Because some project using ws for using ws "features" .

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