mcollovati
commented
9 months ago It could be related to https://github.com/quarkusio/quarkus/issues/11076 and https://github.com/mcollovati/quarkus-hilla/issues/182
It seems the issue could be resolved by installing a RequireBodyHandler
@BuildStep
void requireRequestBodyHandler(BuildProducer<RequireBodyHandlerBuildItem> producer) {
producer.produce(new RequireBodyHandlerBuildItem());
}As a workaround in your application, you can try to manually install the BodyHandler
@ApplicationScoped
public class BodyHandlerInstaller {
public void init(@Observes StartupEvent e, Router httpRouteRouter) {
Handler<RoutingContext> bodyHandler = BodyHandler.create();
httpRouteRouter.route().order(Integer.MIN_VALUE + 1).handler(routingContext -> {
routingContext.request().resume();
bodyHandler.handle(routingContext);
});
}
}
I'll transfer the issue to the vaadin-quarkus repository for further investigation
diversit
DomenicDev
Issue
We're rediscovering Vaadin and in our project we see something similar which can easily be replicated with this 'base-starter' project.
After starting the application, open the browser and hit refresh fast and often, several exceptions occur. See full logs below.
Especially the
2023-10-03 17:01:44,786 WARN [io.ver.cor.imp.BlockedThreadChecker] (vertx-blocked-thread-checker) Thread Thread[vert.x-eventloop-thread-0,5,main] has been blocked for 3941 ms, time limit is 2000 ms: io.vertx.core.VertxException: Thread blockedwe see in our project al lot and then we do not need to refresh that often.Other exception that occurs often is:
2023-10-03 17:01:07,706 ERROR [com.vaa.flo.ser.DefaultErrorHandler] (executor-thread-2) : java.lang.UnsupportedOperationException: Unexpected message id from the client. Expected sync id: 0, got 1. more details logged on DEBUG level.I had a look in the
VaadinServiceclass and where thelockSessionis used on L812. Should that try-catch block not also have afinallyblock like the other try-catch-finally block ? Could be the cause of the locked thread?I did not look at what could have caused the
UnsupportedOperationException.I talked to some Vaadin guys at the current Devoxx conference and he suggested to great an issue here.
Environment
Full logs