We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Accessing EntityManager in WebSocket message handler configured with quarkus.websocket.dispatch-to-worker=true throws javax.enterprise.context.ContextNotActiveException: interface javax.enterprise.context.RequestScoped
quarkus.websocket.dispatch-to-worker=true
javax.enterprise.context.ContextNotActiveException: interface javax.enterprise.context.RequestScoped
Expected behavior EntityManager functionality should proceed.
Actual behavior Processing aborted.
Configuration
Screenshots (If applicable, add screenshots to help explain your problem.)
Environment (please complete the following information):
Additional context https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/quarkus-dev/_XyLtjEJEkQ/KGaxg3ptBwAJ
Applying @ActivateRequestContext to the WebSocket endpoint is an effective work-around.
The text was updated successfully, but these errors were encountered:
Activate request context for websockets
0c4cca6
Fixes quarkusio#9994
a906055
93dd767
Successfully merging a pull request may close this issue.
Describe the bug
Accessing EntityManager in WebSocket message handler configured with
quarkus.websocket.dispatch-to-worker=true
throwsjavax.enterprise.context.ContextNotActiveException: interface javax.enterprise.context.RequestScoped
Expected behavior
EntityManager functionality should proceed.
Actual behavior
Processing aborted.
Configuration
quarkus.websocket.dispatch-to-worker=true
Screenshots
(If applicable, add screenshots to help explain your problem.)
Environment (please complete the following information):
Additional context
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/quarkus-dev/_XyLtjEJEkQ/KGaxg3ptBwAJ
Applying @ActivateRequestContext to the WebSocket endpoint is an effective work-around.
The text was updated successfully, but these errors were encountered: