-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
javax-websocket-tests exception stacktraces #3246
Comments
… logged succeed the callback in EventIdFrameHandler after sending responses in DecoderReaderManySmallTest Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
@lachlan-roberts these exception are indeed showing that the close mechanism is incorrect. You should also test the case of a congested TCP write with an asynchronous close: you won't be able to write the WebSocket close frame because you are TCP congested, and you must idle timeout and hard close the connection. |
Signed-off-by: Greg Wilkins <gregw@webtide.com>
Signed-off-by: Greg Wilkins <gregw@webtide.com>
Signed-off-by: Greg Wilkins <gregw@webtide.com> Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
…tests Issue #3246 - javax-websocket-tests exception stacktraces
the tests in javax-websocet-tests are all passing but produce concerning exception stacktraces which should be investigated
Full Log
The text was updated successfully, but these errors were encountered: