PandacubeFr/PandaLib
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Don't print ClosedChannelException when we actually asked to close the connection.

Browse Source
This commit is contained in:
Marc Baloup 2023-03-18 21:45:39 +01:00
parent 5b40c4aabb
commit e4a5bf0eac
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
pandalib-ws-server/src/main/java/fr/pandacube/lib/ws/server/AbstractServerWS.java
View File

@ -5,12 +5,15 @@ import org.eclipse.jetty.websocket.api.Session;
import org.eclipse.jetty.websocket.api.WebSocketAdapter;
import java.io.IOException;
import java.nio.channels.ClosedChannelException;
import java.time.Duration;
/**
* Minimal implementation of a Websocket server endpoint using the Jetty Websocket API.
*/
public abstract class AbstractServerWS extends WebSocketAdapter implements AbstractWS {
private boolean isClosed = false;
@Override
public final void onWebSocketConnect(Session sess)
@ -37,6 +40,8 @@ public abstract class AbstractServerWS extends WebSocketAdapter implements Abstr
@Override
public final void onWebSocketError(Throwable cause) {
if (isClosed && cause instanceof ClosedChannelException)
return; // ignore because this exception is expected when we just sent a close packet.
onError(cause);
}
@ -53,6 +58,7 @@ public abstract class AbstractServerWS extends WebSocketAdapter implements Abstr
@Override
public final void sendClose(int code, String reason) throws IOException {
getSession().close(code, reason);
isClosed = true;
}
@Override