WebSockets Next: fix the default unhandled-failure-strategy

- do not attempt to close a closed connection and get rid of superfluous WARN message
mkouba · Jun 25, 2024 · 0f64a36 · 0f64a36
1 parent 0484069
commit 0f64a36
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/...s/websockets-next/runtime/src/main/java/io/quarkus/websockets/next/runtime/Endpoints.java b/...s/websockets-next/runtime/src/main/java/io/quarkus/websockets/next/runtime/Endpoints.java
@@ -261,6 +261,9 @@ private static void handleFailure(UnhandledFailureStrategy strategy, Throwable c
     }
 
     private static void closeConnection(Throwable cause, WebSocketConnectionBase connection) {
+        if (connection.isClosed()) {
+            return;
+        }
         connection.close(CloseReason.INTERNAL_SERVER_ERROR).subscribe().with(
                 v -> LOG.debugf("Connection closed due to unhandled failure %s: %s", cause, connection),
                 t -> LOG.errorf("Unable to close connection [%s] due to unhandled failure [%s]: %s", connection.id(), cause,