-
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
NullPointerException in HttpReceiverOverHTTP during WebSocket client Upgrade #5170
Comments
This is probably due to Issue #4971 and we likely missed a step on the websocket side related to that change. |
I managed to reproduce this with some logging enabled. Looks like the
|
@lachlan-roberts this is a classic case where the HTTP response finishes before the HTTP request. When the response completes, it nulls out The simple fix is to add a null guard in |
Signed-off-by: Lachlan Roberts <[email protected]>
…ffer Issue #5170 - fix NPE during websocket upgrade
Signed-off-by: Lachlan Roberts <[email protected]>
Issue #5170 - fix upgrade bug in HttpReceiverOverHTTP
Reopening to verify that this issue does not exist in |
Signed-off-by: Lachlan Roberts <[email protected]>
Signed-off-by: Lachlan Roberts <[email protected]>
Issue #5170 - backport fixes for WebSocket upgrade to jetty-9.4.x
Fixed in |
Jetty version
10.0.x
Description
Had this exception come up a few times in different websocket tests. This stack trace is from
WebSocketStatsTest
.This seems to occur very infrequently, have to run the test many times for this to have a chance of happening.
The text was updated successfully, but these errors were encountered: