-
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
Problem with quarkus-websockets on 2.0.0.Alpha1 #16753
Comments
This also affect |
@geoand could you triage, I am not sure who to ping on this beside @cescoffier. |
Looks like the fix for this did not go into the 4.x branch |
Hum, possibly. I remember having a hard time rebasing the WebSocket split. Maybe I missed something. |
Now that it has been merged we just need a release from the current main branch. |
@stuartwdouglas do you want me to cut a release of quarkus-http? Would be good to have it integrated before the second alpha. |
If you have time that would be great |
Ok, working on it! |
@stuartwdouglas I just run into that issue on my own project. Then i tried this reproducer with 2.0.0.CR2 and it also failed. |
@stuartwdouglas I can confirm I was able to reproduce it with |
I have also encountered this problem, please let me know if there is a possible solution |
Describe the bug
With quarkus
main
branch, I get this exception when sending a websocket message (no problem with1.13.2.Final
):Expected behavior
Should work
Actual behavior
Exception and not working
To Reproduce
https://github.com/ia3andy/reproducer-websocket
The reproducer use the websocket example codestart which is very close to the quickstart.
Steps to reproduce the behavior:
Environment (please complete the following information):
Output of
uname -a
orver
Output of
java -version
Quarkus version or git rev
999-SNAPSHOT
Build tool (ie. output of
mvnw --version
orgradlew --version
)CC @cescoffier
The text was updated successfully, but these errors were encountered: