Syslog wisej-servcer.lic io error and Object reference not found or set to an instance of an object.

0
0

System: Debian 11, WiseJ 3.1.2, Dotnet 6.0.404

While reviewing our syslog we are noticing the following error every 30 seconds roughly.

Mar 19 10:29:01 wisej1 dotnet: onemci Error: 0 :
Mar 19 10:29:01 wisej1 dotnet: System.IO.IOException: The file ‘/opt/[our_app]/wisej-server.lic’ already exists.
Mar 19 10:29:01 wisej1 dotnet: onemci Information: 0 :
Mar 19 10:29:01 wisej1 dotnet: RefreshAll:

Not sure if the two are related. We are also attaching a screenshot of an error that appears after the system is in use for a few hours. The message box shows before a user does any interaction such as clicking the login button and there is no code in the load event.  If we restart the wisej application using systemctl the “Object reference not found or set to an instance of an object” error goes away for a little while but then returns.

Mar 19 10:34:48 wisej1 dotnet-[our_app]-service[2136323]: #033[41m#033[30mfail#033[39m#033[22m#033[49m: Microsoft.AspNetCore.Server.Kestrel[13]
Mar 19 10:34:48 wisej1 dotnet-[our_app]-service[2136323]: Connection id “0HMP8C9HT46IF”, Request id “0HMP8C9HT46IF:00000002”: An unhandled exception was thrown by the application.
Mar 19 10:34:48 wisej1 dotnet-[our_app]-service[2136323]: System.Net.WebSockets.WebSocketException (0x80004005): The remote party closed the WebSocket connection without completing the close handshake.
Mar 19 10:34:48 wisej1 dotnet-[our_app]-service[2136323]: at System.Net.WebSockets.ManagedWebSocket.ThrowIfEOFUnexpected(Boolean throwOnPrematureClosure)
Mar 19 10:34:48 wisej1 dotnet-[our_app]-service[2136323]: at System.Net.WebSockets.ManagedWebSocket.EnsureBufferContainsAsync(Int32 minimumRequiredBytes, CancellationToken cancellationToken, Boolean throwOnPrematureClosure)
Mar 19 10:34:48 wisej1 dotnet-[our_app]-service[2136323]: at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
Mar 19 10:34:48 wisej1 dotnet-[our_app]-service[2136323]: at System.Net.WebSockets.ManagedWebSocket.ReceiveAsyncPrivate[TResult](Memory`1 payloadBuffer, CancellationToken cancellationToken)
Mar 19 10:34:48 wisej1 dotnet-[our_app]-service[2136323]: at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token)
Mar 19 10:34:48 wisej1 dotnet-[our_app]-service[2136323]: at System.Threading.Tasks.ValueTask`1.ValueTaskSourceAsTask.<>c.<.cctor>b__4_0(Object state)
Mar 19 10:34:48 wisej1 dotnet-[our_app]-service[2136323]: — End of stack trace from previous location —
Mar 19 10:34:48 wisej1 dotnet-[our_app]-service[2136323]: at Wisej.Core.HttpHandler.ProcessWebSocketRequest(HttpContext context)
Mar 19 10:34:48 wisej1 dotnet-[our_app]-service[2136323]: at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)

Attachment
  • You must to post comments
0
0

I have attached a screen shot of the inner error.

It appeared after the site was running for about 10 hours.

  • Luca (ITG)
    Thank you. I think it was fixed a while ago. Try with the latest build.
  • Chad Miller
    Upgrading to latest build fixed the issue, thank you.
  • You must to post comments
0
0

The two are not related.

For the null reference exception, if you set debug mode on you will also see the stack trace in the error message. Or you can use the Application.ThreadException event to handle it in code and look at the stack trace. Or you can attach VS in debug mode and enable the debug->exception settings to break when thrown.

The file already exists is handled.

 

  • Chad Miller
    I posted the captured inner exception on this thread with a screenshot.
  • You must to post comments
Showing 2 results
Your Answer

Please first to submit.