socket.io-client-csharp
socket.io-client-csharp copied to clipboard
doghappy
unhandled exception
hi i have a service that is sending stuff to another service and today the sending service crashed with this error message: _Application: Mirsk.RSR.IBM.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.InvalidOperationException at System.Net.WebSockets.ClientWebSocket.ThrowIfNotConnected() at System.Net.WebSockets.ClientWebSocket.SendAsync(System.ArraySegment`1<Byte>, System.Net.WebSockets.WebSocketMessageType, Boolean, System.Threading.CancellationToken) at SocketIOClient.WebSocketClient.ClientWebSocket+<SendMessageAsync>d__13.MoveNext() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task) at SocketIOClient.WebSocketClient.ClientWebSocket+<SendMessageAsync>d__12.MoveNext() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task) at SocketIOClient.Processors.PingProcessor+<Process>d__0.MoveNext() at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__6_1(System.Object) at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading.ThreadPoolWaitCallback.PerformWaitCallback()
how can this error bring down my service. when is this code even executed? I have a try catch around the EmitAsync call, so i don't really understand this. I guess that the task that EmitAsync creates is the one failing, but it should not bring down the hole service.
