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

Issue-1160 Added java.lang.Error handling in WebSocketImpl and WebSocketServer #1223

Merged
merged 8 commits into from
Mar 25, 2022

Conversation

Serpion-ua
Copy link
Contributor

@Serpion-ua Serpion-ua commented Mar 24, 2022

Added java.lang.Error handling in WebSocketImpl and WebSocketServer. Fatal Error ( VirtualMachineError | ThreadDeath | LinkageError ) lead to stopping of WebSocketServer. Now non-fatal Error leads to closing of web socket but not stopping of WebSocketServer.

Fixes #1160

Oleg Aleksandrov and others added 2 commits March 24, 2022 17:04
Issue-1160 Added java.lang.Error handling in WebSocketImpl and WebSocketServer
@Marcono1234
Copy link

When wrapping the Error in an Exception it might be good to preserve its stack trace, e.g. by using new Exception(e) instead of new Exception(e.getMessage()).

Oleg Aleksandrov and others added 3 commits March 24, 2022 22:18
Issue-1160 Put whole Error into Exception during Error processing, not just stack trace
@Serpion-ua
Copy link
Contributor Author

When wrapping the Error in an Exception it might be good to preserve its stack trace, e.g. by using new Exception(e) instead of new Exception(e.getMessage()).

@Marcono1234 yeap, changed

@marci4 marci4 requested a review from PhilipRoman March 25, 2022 06:21
@marci4
Copy link
Collaborator

marci4 commented Mar 25, 2022

@Serpion-ua thank you very much for your contribution!

@PhilipRoman thank you for your review!

@marci4 marci4 merged commit 46ae001 into TooTallNate:master Mar 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

WebSocketWorker does not handle Throwable
5 participants