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

Connection variable is not set to false when WebSocket receives DISCONNECT #123

Open
jasons-medistaff opened this issue Jan 30, 2023 · 1 comment
Assignees

Comments

@jasons-medistaff
Copy link

When the client actively disconnects or unsubscribes, "connection" variable is correctly set to false. However, when the client receives a DISCONNECT packet, the WebSocket is successfully torn down, but the "connection" variable remains true.

We have code that checks for isConnected(), and rebuild the connection if it is false. Since the "connection" variable is not set to false, we do not have a way to check if the WebSocket connection is active or not.

As a workaround, we change the "connection" variable inside the stompClientDidDisconnect function. However, we are afraid that this may cause problems inside the Stomp library code.

Is there a reason why "connection" variable is only set to false when the client disconnects and not when the connection is shutdown?

@stale
Copy link

stale bot commented May 21, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label May 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants