From 1320fed7fef6d8be480a020d46ae9a0bff4a131f Mon Sep 17 00:00:00 2001 From: Rossen Stoyanchev Date: Tue, 2 Oct 2018 09:35:14 -0400 Subject: [PATCH] Use WebsocketOutbound#sendClose Switch to using the sendClose method available since Reactor Netty 0.8 vs explicitly sending a CloseWebSocketFrame. Related to SPR-17306, but does not address the root cause. --- .../reactive/socket/adapter/ReactorNettyWebSocketSession.java | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/spring-webflux/src/main/java/org/springframework/web/reactive/socket/adapter/ReactorNettyWebSocketSession.java b/spring-webflux/src/main/java/org/springframework/web/reactive/socket/adapter/ReactorNettyWebSocketSession.java index c0c812d26f..140bce6240 100644 --- a/spring-webflux/src/main/java/org/springframework/web/reactive/socket/adapter/ReactorNettyWebSocketSession.java +++ b/spring-webflux/src/main/java/org/springframework/web/reactive/socket/adapter/ReactorNettyWebSocketSession.java @@ -15,7 +15,6 @@ */ package org.springframework.web.reactive.socket.adapter; -import io.netty.handler.codec.http.websocketx.CloseWebSocketFrame; import io.netty.handler.codec.http.websocketx.WebSocketFrame; import org.reactivestreams.Publisher; import reactor.core.publisher.Flux; @@ -98,8 +97,7 @@ public class ReactorNettyWebSocketSession @Override public Mono close(CloseStatus status) { - WebSocketFrame closeFrame = new CloseWebSocketFrame(status.getCode(), status.getReason()); - return getDelegate().getOutbound().sendObject(closeFrame).then(); + return getDelegate().getOutbound().sendClose(status.getCode(), status.getReason()); }