-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
The websocket client is closed, but messages are still being received. #753
Comments
Below is the code and log. After receiving the message that the server closes the websocket, the message can still be received and processed. But I don't want to continue processing messages after closing
At this time, the websocket is already connected and the message is received.
At this time, the websocket is closed.
At this time, the websocket has been closed, but messages can still be received.
|
The websocket client is closed, but there are still messages being received. Our business wants the old messages to be discarded, but we have not found the code to clear the message queue. Is this a special scenario? Or in most scenarios, after the connection is closed, we still want the client to process the received messages.
The text was updated successfully, but these errors were encountered: