florinciubotariu
commented
4 years ago Happened again today. One of our three instances was affected and I had to restart it.
It seems that those weird exceptions started appearing after a CommitFailedException:
System.Data.Entity.Infrastructure.CommitFailedException: An error was reported while committing a database transaction but it could not be determined whether the transaction succeeded or failed on the database server. See the inner exception and http://go.microsoft.com/fwlink/?LinkId=313468 for more information.
---> System.Data.SqlClient.SqlException (0x80131904): Resource ID : 1. The request limit for the database is 200 and has been reached. See 'http://go.microsoft.com/fwlink/?LinkId=267637' for assistance.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action<T> wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.TdsExecuteTransactionManagerRequest(Byte[] buffer, TransactionManagerRequestType request, String transactionName, TransactionManagerIsolationLevel isoLevel, Int32 timeout, SqlInternalTransaction transaction, TdsParserStateObject stateObj, Boolean isDelegateControlRequest)
at System.Data.SqlClient.SqlInternalConnectionTds.ExecuteTransactionYukon(TransactionRequest transactionRequest, String transactionName, IsolationLevel iso, SqlInternalTransaction internalTransaction, Boolean isDelegateControlRequest)
at System.Data.SqlClient.SqlInternalTransaction.Commit()
at System.Data.SqlClient.SqlTransaction.Commit()
at System.Data.Entity.Infrastructure.Interception.InternalDispatcher<T>.Dispatch<TTarget,TInterceptionContext>(TTarget target, Action<T1,T2> operation, TInterceptionContext interceptionContext, Action<T1,T2,T3> executing, Action<T1,T2,T3> executed)
ClientConnectionId:x
Error Number:10928,State:1,Class:20
ClientConnectionId before routing:x
Routing Destination:x.tr45.northeurope1-a.worker.database.windows.net,11484
--- End of inner exception stack trace ---
at System.Data.Entity.Infrastructure.Interception.InternalDispatcher<T>.Dispatch<TTarget,TInterceptionContext>(TTarget target, Action<T1,T2> operation, TInterceptionContext interceptionContext, Action<T1,T2,T3> executing, Action<T1,T2,T3> executed)
at System.Data.Entity.Infrastructure.Interception.DbTransactionDispatcher.Commit(DbTransaction transaction, DbInterceptionContext interceptionContext)
at System.Data.Entity.Core.EntityClient.EntityTransaction.Commit()
at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransactionAsync<T>(Func<T> func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess, CancellationToken cancellationToken)
at System.Data.Entity.Core.Objects.ObjectContext.SaveChangesToStoreAsync(SaveOptions options, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, CancellationToken cancellationToken)
at System.Data.Entity.Infrastructure.DbExecutionStrategy.ProtectedExecuteAsync<TResult>(Func<T> operation, CancellationToken cancellationToken)
at System.Data.Entity.Core.Objects.ObjectContext.SaveChangesInternalAsync(SaveOptions options, Boolean executeInExistingTransaction, CancellationToken cancellationToken)
jdaigle
You can see in the screenshot the lifetime of our pod. When I saw exceptions flooding I immediately logged the stdout to a log file and killed it.
roji
melsaqqa
ajcvickers
1Jesper1
anmesh4899
Describe what is not working as expected.
There was an incident on our production environment. We have two instances of the same application (backend). A client made around 2.5k requests at the same time (1.25k / app).
The first issue which appeared is the following exception:
that is expected taking into consideration the number of concurrent HTTP requests. After that our both applications started throwing a lot of random exceptions as you can see in the following picture:
I will paste some stacktraces below:
Useful information
Our context:
DatabaseFactory:
Unfortunately, we use another layer above EF: Generic Repository & UoW Patterns where we inject into constructor the
IDatabaseFactory. We useMicrosoft.Extensions.DependencyInjection.Abstractions 3.1.2for DI. The registrations areScoped. We useasync all the way down.People with same problem:
https://stackoverflow.com/questions/50560257/entity-framework-throws-unexpected-exceptions-with-a-heavy-workload https://stackoverflow.com/questions/35896100/strange-error-in-sql-server-from-asp-net-app https://stackoverflow.com/questions/47076273/getting-exception-suddenly-from-entityframework https://stackoverflow.com/questions/41839754/entity-framework-6-1-3-invalidoperationexception-after-a-few-days-of-running https://stackoverflow.com/questions/35011086/ef-randomly-sees-wrong-property-type
Further technical details
I have a .NET Framework project with the EDMX. After I generate the entities, I run a powershell script to move them to the .NET Standard 2.1 project.