-
Notifications
You must be signed in to change notification settings - Fork 563
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unhandled Exception in SocketInitiator.OnStart() can Terminate Process #833
Comments
#834 doesn't solve the root cause, but it does provide a layer of protection for the application from current/future exceptions that occur in the loop. |
Did you see this exception when running 1.11.2? I've done a lot of work in the past month updating files to use proper nullable ( However, I haven't finished nullable-izing all the classes yet, so I'm not surprised that the null-risk is still present. The try/catch is a good step for now. I'll add it in. If you are able to get a full stacktrace on the null, please let me know. |
We ran into the issue while running 11.0.0. Nice, I'll keep an eye out for the changes! I'll fix up the missing |
I'll get it on my branch. It ties into that other issue I'm working on anyway. Thanks |
Just saw your comment regarding the logger on PR. Sounds good, thanks! |
Hey @gbirchmeier, unfortunately this took our server down again today - any word on the |
@Falcz I'm hoping to get it out in the next month or two. There are 3 open issues I want to get into it. |
Awesome, thanks! |
We ran into a case of our process terminating due to unhandled exception on a dedicated thread:
I suspect the
sessionId
coming in fromdisconnected
isn't being found duringLookupSession
, but I haven't managed to catch it in the act.The text was updated successfully, but these errors were encountered: