InvalidOperationException in DbConnectionInternal
Posted: Thu 21 Aug 2014 13:34
With Devart 7.9.333 we ran into a bug at a production site:
Application: MyCompany.BusinessWorkflows.Server.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info:
This application is using both EntityFramework as well as ADO calls. The ado calls are made in direct mode without pooling (at least according to the connection string), while EF uses pooling (this is why I posted it in EF support).
Do you know of anything that can trigger this behavior?
Is this a known behavior in 7.9?
Is there a newer 7.x version that's binary compatible to 7.9 we can upgrade to and which solves this problem?
Application: MyCompany.BusinessWorkflows.Server.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info:
Code: Select all
System.InvalidOperationException Stack: at Devart.Common.DbConnectionInternal.d(System.Object) at Devart.Common.DbConnectionPoolGroup.a(Devart.Common.DbConnectionPool) at Devart.Common.DbConnectionPoolGroup.a(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.TimerQueueTimer.CallCallback() at System.Threading.TimerQueueTimer.Fire() at System.Threading.TimerQueue.FireNextTimers()
Do you know of anything that can trigger this behavior?
Is this a known behavior in 7.9?
Is there a newer 7.x version that's binary compatible to 7.9 we can upgrade to and which solves this problem?