-
Notifications
You must be signed in to change notification settings - Fork 38.4k
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
Avoid logging exception for closed session in AbstractSockJsSession #24986
Comments
It means the session was closed simultaneously while a message was being processed and as a result it was dropped. We could avoid throwing the exception there but just do a debug message since there isn't much that could be done. |
@rstoyanchev Thanks for your feedback, it makes sense. Is there a way to catch this exception and avoid displaying it ? |
We can make sure it's not displayed. |
@mbenmass I intend to make a change for this. |
Backport of e17736d. Closes spring-projectsgh-24986
I have the following WebSocket configuration :
I have around 30 JS clients connected to my server using SockJS to send messages. From time to time I get the following error :
I have no idea why I do get such an error as the logs are not self-explanatory.
I have been looking eveywhere in the internet, but I didn't find any solution to this issue, or at least someone who can explain what is happening.
Grateful if an experienced programmer with Spring and Websocket could help.
The text was updated successfully, but these errors were encountered: