Closed Koekebakkert closed 2 weeks ago
Probably a duplicate of vaadin/quarkus#138
Although the exception looks the same the situation is quite different. There is no UnsupportedOperationException
and I cannot summon the exception without using the @Push
annotation on the starter code.
Although the exception looks the same the situation is quite different. There is no
UnsupportedOperationException
and I cannot summon the exception without using the@Push
annotation on the starter code.
I'm experiencing the same issue. It seems to happen if there is an exception while executing the push. this request then seems not to be terminated correctly
The workaround in this comment seems to work for me on the starter project.
Thanks Marco! I can confirm that it also solves the thread blocked exception in the findVaadinSession case of this issue in dev mode for all my quarkus vaadin applications.
Closing as potential duplicate of #138
Description of the bug
All my Vaadin Quarkus push enabled applications run into Vertx Thread blocked exceptions during findVaadinSession quite often (but not always). The actual vaadin browser session will hang during the block. The behavior occurs in both dev mode and production mode.
The stack traces look like this on startup but the same exception also occur later when a new session is created:
Expected behavior
No blocking exception occurs and the browser session runs smoothly.
Minimal reproducible example
Download the sample application from:
Add
@Push
to the class com.example.starter.base.AppConfig.Run the application, e.g.
quarkus dev
or
mvn quarkus:dev
With a supported webbrowser goto
http://localhost:8080
If the exceptions do not occur immediately, just refresh the page a couple of times.
Also the following exception will occur:
Versions