-
Notifications
You must be signed in to change notification settings - Fork 2.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
NPE in websockets-next #42271
Comments
cc @mkouba |
Hm, this could only happen if an @RobertoUa Could you tell me a little bit more about your application/use case? |
it happens every time the connection is terminated abruptly. Reproduces every time when I connect with I also don't think it's a timeout from reverse proxy/load balancer, I do pings and connections could stay alive for hours. |
- fix invocation of OnClose callback with a CloseReason param - resolves quarkusio#42271
Yes, I was able to reproduce the problem locally. There's not much we can do about it though. I've modified the code to use |
- fix invocation of OnClose callback with a CloseReason param - resolves quarkusio#42271 (cherry picked from commit 983b8bf)
- fix invocation of OnClose callback with a CloseReason param - resolves quarkusio#42271
Describe the bug
Getting NPE
It seems like error is happening here
quarkus/extensions/websockets-next/runtime/src/main/java/io/quarkus/websockets/next/runtime/WebSocketConnectionBase.java
Line 134 in 450681e
closeStatusCode
isShort
and it's null. It throws when it tries to unbox (Short
->short
)Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: