-
Notifications
You must be signed in to change notification settings - Fork 10
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
Graceful handling of connection issues #86
Comments
Full stacktrace, it seems to be the Gloebit user get method. The connection to the database needs a few try catch to make sure connect failures don't terminate. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems when there is a failure to connect to the Gloebit database that failure is not handled gracefully and causes termination of the process, something that modules should try to avoid if possible.
Stacktrace: Exception: MySql.Data.MySqlClient.MySqlException (0x80004005): Reading from the stream has failed. ---> System.IO.IOException: Unable to read data from the transport connection: Operation on non-blocking socket would block. ---> System.Net.Sockets.SocketException: Operation on non-blocking socket would block
at System.Net.Sockets.Socket.Receive (System.Byte[] buffer, System.Int32 offset, System.Int32 size, System.Net.Sockets.SocketFlags socketFlags) [0x00016] in <4bf78e13a6ea4494a3898e6a836a77f4>:0
at System.Net.Sockets.NetworkStream.Read (System.Byte[] buffer, System.Int32 offset, System.Int32 size) [0x00065] in <4bf78e13a6ea4494a3898e6a836a77f4>:0
Ideally this would not cause a full termination rather just a delayed retry or disabling the module for the time being until the simulator is restarted. I will see if I can find the code and add some graceful handling, but you know it better so please have a look also.
The text was updated successfully, but these errors were encountered: