WebSocket error handling #4740

Activity

1. itg-assistant commented on Jun 16, 2026

   

   itg-assistantbot

   on Jun 16, 2026

   Author

   More actions

   Julie (ITG) answered 2025-03-27 13:08:58 UTC

   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
2. itg-assistant

   added

   BugSomething is broken or behaving unexpectedly.Something is broken or behaving unexpectedly.

   on Jun 16, 2026
3. itg-assistant commented on Jun 16, 2026

   

   itg-assistantbot

   on Jun 16, 2026

   Author

   More actions

   Dino Novak answered 2025-04-02 13:38:53 UTC

   Hi,
   this is a follow up error when Wisej App crashes due to error described here
   https://wisej.com/support/question/unknown-function-updatechildzorder-1

   Above mentioned error occurs, app crashes and then I get this as a followup error for all connected clients

   The only recovery is stop AppPool, restart of Web Service and AppPool restrat
4. itg-assistant commented on Jun 16, 2026

   

   itg-assistantbot

   on Jun 16, 2026

   Author

   More actions

   Frank (ITG) answered 2025-04-02 14:19:31 UTC

   Hi Dino,

   in order to help you and investigate this we need a reproducible test case.

   Best regards
   Frank
5. itg-assistant commented on Jun 16, 2026

   

   itg-assistantbot

   on Jun 16, 2026

   Author

   More actions

   Dino Novak answered 2025-04-02 16:26:14 UTC

   Hi
   unfortunately I am not successful in creating a test case where this would consistently pop us as problem,
   but let me share with you what is in place in order to try to catch this:

   1. We are restarting app pool daily before each workday in order to remove potential memory issues

   2. we do not see significant memory utilisation that could be linked to this error

   3. we are running app in non managed app pool with latest .net 8 and wisej binaries

   4. we tried running app with websockets enabled and disabled and in both cases this error pops up

   5. binary is configured in web.config to run with stdoutLogEnabled=”true” stdoutLogFile=”.\logs\stdout” hostingModel=”inprocess” and with

   6. In program.cs we have serology enabled with log to file and are defining thread handler
      Application.ThreadException += new ThreadExceptionEventHandler(Application_ThreadException);

   private static void Application_ThreadException(object sender, System.Threading.ThreadExceptionEventArgs e)
   {
   // Log the exception or show a message to the user
   LogException(e.Exception);
   ShowErrorMessage(e.Exception);
   }

   7. in startup.cs we added
      app.UseExceptionHandler(
      options =>
      {
      options.Run(
      async context =>
      {

               context.Response.StatusCode = (int)HttpStatusCode.InternalServerError;
               context.Response.ContentType = “text/html”;
               var ex = context.Features.Get();
               if (ex != null)
               {
                   Log.Error($”Error: {ex.Error.Message} : {ex.Error.StackTrace}”);
                   var err = $”Error: {ex.Error.Message}{ex.Error.StackTrace}”;
                   await context.Response.WriteAsync(err).ConfigureAwait(false);
               }
           });
      

      }
      );

   And unfortunately we are unable to trace any appearance of this error.
   So any advice from your side would be more than welcomed.
6. itg-assistant

   closed this as completedon Jun 16, 2026