Downgrade expected WebSocket disconnect exceptions from Error to Debug

[Copilot]

Normal WebSocket disconnections (server restart, network jitter, client close) were generating ObjectDisposedException, SocketException, and WebSocketException at ERROR level in the DoPull receive loops, flooding logs and masking real errors.

Changes

WsChannel.cs (non-NETCOREAPP client)

• Added protected static IsNormalDisconnect(SocketError) helper — matches ConnectionReset (10054), ConnectionAborted (10053), OperationAborted (995)
• New catch clauses before the generic Exception handler:
  • ObjectDisposedException → silent break
  • SocketException matching normal codes → Debug log + break

WsChannelCore.cs (NETCOREAPP client, System.Net.WebSockets)

• Same ObjectDisposedException and SocketException handling (reuses IsNormalDisconnect from base class)
• Additional catch for WebSocketException when WebSocketErrorCode == ConnectionClosedPrematurely or socket.State == Aborted → Debug log + break, replacing the previous ad-hoc inline suppression

// Before: all unexpected exceptions logged as Error
catch (Exception ex)
{
    if (source.IsCancellationRequested) break;
    if (ex is not WebSocketException || socket.State != WebSocketState.Aborted)
        _client.Log?.Error("[{0}]WebSocket异常[{1}]: {2}", ...);
    if (ex is WebSocketException) break;
}

// After: normal disconnects caught early, only genuine errors reach Error
catch (ObjectDisposedException) { break; }
catch (WebSocketException wex) when (
    wex.WebSocketErrorCode == WebSocketError.ConnectionClosedPrematurely ||
    socket.State == WebSocketState.Aborted)
{
    _client.Log?.Debug("[{0}]WebSocket连接断开[{1}]", _client.Name, wex.WebSocketErrorCode);
    break;
}
catch (SocketException sex) when (IsNormalDisconnect(sex.SocketErrorCode))
{
    _client.Log?.Debug("[{0}]WebSocket连接断开[{1}]", _client.Name, sex.SocketErrorCode);
    break;
}
catch (Exception ex)
{
    if (source.IsCancellationRequested) break;
    _client.Log?.Error("[{0}]WebSocket异常[{1}]: {2}", ...);
    if (ex is WebSocketException) break;
}

[Copilot]

Pull request overview

This PR reduces log noise in the WebSocket client receive loops by treating expected disconnect-related exceptions (e.g., disposal, connection resets, premature close) as normal termination conditions, logging them at Debug (or silently breaking) instead of Error.

Changes:

• Added explicit handling for ObjectDisposedException and “normal” SocketException disconnect codes in WsChannel.DoPull.
• Added explicit handling for ObjectDisposedException, “normal” SocketException, and selected WebSocketException disconnect scenarios in WsChannelCore.DoPull.
• Introduced a shared IsNormalDisconnect(SocketError) helper to standardize what’s considered a normal disconnect.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
NewLife.Remoting/Clients/WsChannel.cs	Adds normal-disconnect detection (IsNormalDisconnect) and downgrades common disconnect exceptions to non-error handling in the receive loop.
NewLife.Remoting/Clients/WsChannelCore.cs	Adds normal-disconnect handling for WebSocketException/SocketException in the NETCOREAPP receive loop to avoid flooding Error logs on expected disconnects.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.