From f64b5d9c0861215ae833907146ec5fc2b2d236cc Mon Sep 17 00:00:00 2001 From: Martin Kouba Date: Thu, 19 Mar 2026 16:55:28 +0100 Subject: [PATCH] Vert.x: do not disable websockets extensions init if websockets-next is present - there's an optimization introduced in #31715 that disables WebSockets extensions initialization if the legacy quarkus-websocket is not present, it should be quarkus-websocket && quarkus-websocket-next - fixes #53159 --- .../io/quarkus/vertx/http/deployment/VertxHttpProcessor.java | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/extensions/vertx-http/deployment/src/main/java/io/quarkus/vertx/http/deployment/VertxHttpProcessor.java b/extensions/vertx-http/deployment/src/main/java/io/quarkus/vertx/http/deployment/VertxHttpProcessor.java index 7327c4c471577..bc14b6032d62d 100644 --- a/extensions/vertx-http/deployment/src/main/java/io/quarkus/vertx/http/deployment/VertxHttpProcessor.java +++ b/extensions/vertx-http/deployment/src/main/java/io/quarkus/vertx/http/deployment/VertxHttpProcessor.java @@ -561,7 +561,9 @@ void openSocket(ApplicationStartBuildItem start, eventLoopCount.getEventLoopCount(), websocketSubProtocols.stream().map(bi -> bi.getWebsocketSubProtocols()) .collect(Collectors.toList()), - launchMode.isAuxiliaryApplication(), !capabilities.isPresent(Capability.VERTX_WEBSOCKETS)); + launchMode.isAuxiliaryApplication(), + !capabilities.isPresent(Capability.VERTX_WEBSOCKETS) + && !capabilities.isPresent(Capability.WEBSOCKETS_NEXT)); } @BuildStep