I am experiencing strange web socket errors. is there a way to create a handler that would help me determine if this is caused by timeouts or something else ?
How wisej is handling “sessionTimeout” from Default.json, could this be connected to this web socket errors ?
Another question is how you can restart non managed app pool, sometimes if I try to do it from IIS console I am just getting Event Viewer log file failed to stop app pool.
This is
fail: Microsoft.AspNetCore.Server.IIS.Core.IISHttpServer[2]
Connection ID “15348267531689264185”, Request ID “8000043a-0000-d500-b63f-84710c7967bb”: An unhandled exception was thrown by the application.
System.Net.WebSockets.WebSocketException (0x80004005): The remote party closed the WebSocket connection without completing the close handshake.
at System.Net.WebSockets.ManagedWebSocket.ThrowEOFUnexpected()
at System.Net.WebSockets.ManagedWebSocket.EnsureBufferContainsAsync(Int32 minimumRequiredBytes, CancellationToken cancellationToken)
at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
at System.Net.WebSockets.ManagedWebSocket.ReceiveAsyncPrivate[TResult](Memory`1 payloadBuffer, CancellationToken cancellationToken)
at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token)
at System.Threading.Tasks.ValueTask`1.ValueTaskSourceAsTask.<>c.<.cctor>b__4_0(Object state)
— End of stack trace from previous location —
at Wisej.Core.HttpHandler.ProcessWebSocketRequest(HttpContext context)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Server.IIS.Core.IISHttpContextOfT`1.ProcessRequestAsync()
It’s not an error to be handled and cannot be handled, it’s already managed by the System.Net.WebSocket library which is not part of Wisej. It’s a normal occurrence for the System.Net.WebSockets.ManagedWebSocket. You found it in the event viewer, not in the application. It’s the websocket throwing an exception of a connection terminated for a variety of reasons.
Julie
Please login first to submit.