net no exception thrown for deadlock sql

#Net no exception thrown for deadlock sql code

nested exception is : Transaction (Process ID 55) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. : Hibernate operation: could not delete: SQL Transaction (Process ID 55) was deadlocked on lock resources with another process and has been chosen as the deadlock victim.

url: /confluence/pages/docreatepage.action | userName: tstcreator3 17:01:21,359 ERROR onThrowable Invoking rollback for transaction on action '/pages/docreatepage.action (CreatePageAction.doAdd())' due to throwable: : Hibernate operation: could not delete: SQL Transaction (Process ID 55) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. 17:01:21,357 ERROR execute Could not synchronize database state with session 17:01:21,355 ERROR logExceptions Transaction (Process ID 55) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. url: /confluence/pages/docreatepage.action | userName: tstcreator3 | action: docreatepage They're mostly related to poor query design, broken DB configuration, or too much dataĬase SqlErrorCode.17:01:21,355 ERROR logExceptions Transaction (Process ID 55) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. The following errors are probably not going to resolved in 10 seconds Therefore we need to retry it, even though it seems this problem wouldn't fix itselfĬase SqlErrorCode.DatabaseWorkerThreadThrottling:Ĭase SqlErrorCode.ServerWorkerThreadThrottling:

#Net no exception thrown for deadlock sql code

this error code is sometimes sent by the client when it shouldn't be so we can't make any conclusions from itĬase SqlErrorCode.EncryptionNotSupported: This is a very non-specific error, can happen for almost any reason

SqlErrorCode code = GetSqlErrorCodeFromInt(error.Number) Private void ParseErrors(IEnumerable errors) Select new SqlErrorWrapper(err)).Cast().ToList() Public SqlExceptionDetails(IEnumerable errors) : this() Public SqlExceptionDetails(SqlException exception) :this(()) This.OperationsThrottled = OperationsThrottled.None

This.SlightlyExceededResources = ResourcesThrottled.None This.SeriouslyExceededResources = ResourcesThrottled.None With this simple-fake-naive CanRetry() function: private static readonly int RetriableClasses = Wrap everything in try/ finally to properly dispose connection. What to do? Handle that here, also checking Number property. Each error is SqlError: foreach (SqlError error in exception.Errors)Įach SqlError has a Class property you can use to roughly determine if you can retry or not (and in case you retry if you have to recreate connection too). You can iterate through them with Errors property. One single SqlException (may) wraps multiple SQL Server errors. Using (SqlDataReader reader = command.ExecuteReader()) Using (SqlCommand command = connection.CreateCommand()) Is there a commonly used pattern in C# for dealing with things like this? For example, is there a property I can check on the SqlConnection object to detect failed connections? If not, what is the best way to approach this problem?įor what it is worth, my code isn't anything special: using (SqlConnection connection = new SqlConnection(m圜onnectionString)) My question is this: what is the best way to distinguish between environmental problems (lost connections, time-outs) and other kinds of exceptions (things like logical errors that would have happened even if the environment was stable). I just want those to bubble the exception up to the client. At the same time, I don't want to retry queries if they've failed for logical errors. To do so, I want to retry operations that are the result of infrastructure failures such as network glitches, SQL servers going off-line because they're being rebooted, query time-outs etc. There is nothing I can do to address the environmental issues, so I need to handle them as gracefully as possible. I have a C# application that fetches data from SQL Server hosted in a somewhat flaky environment.