实体框架自定义执行策略未调用查询

如何解决实体框架自定义执行策略未调用查询

我已经在My custom DbExecutionStrategy is not being called阅读了问题(包含更新),但认为不是同一问题。

我编写了一个自定义执行策略,并包含了日志信息,因此我知道何时调用它。但是,我仍然从查询中获得SQL死锁,没有迹象表明正在调用我的自定义执行策略。

自定义执行策略:

using System;
using System.Data.Entity.Infrastructure;
using System.Data.SqlClient;
using System.Diagnostics;
using log4net;

namespace MyDataModel
{
    // Based on https://stackoverflow.com/questions/13159326/implementing-retry-logic-for-deadlock-exceptions
    // and https://www.codeproject.com/Tips/758469/Implementing-Connection-Resiliency-with-Entity-Fra

    public class CustomExecutionStrategy : DbExecutionStrategy
    {
        private int _totalFailures;

        public CustomExecutionStrategy()
        {
        }

        public CustomExecutionStrategy(int maxRetryCount,TimeSpan maxDelay)
            : base(maxRetryCount,maxDelay)
        {
        }

        public static string StackTrace()
        {
            var st = new StackTrace();
            var sfs = st.GetFrames();

            var result = string.Empty;

            foreach (var sf in sfs)
            {
                var method = sf.GetMethod();
                result += (string.IsNullOrEmpty(result) ? string.Empty : "->") + method.DeclaringType.Name + "." + method.Name;
            }

            return result + " ";
        }

        protected override bool ShouldRetryOn(Exception exception)
        {
            var log = LogManager.GetLogger("Logger");

            if (exception is TimeoutException)
            {
                _totalFailures++;
                log.Info($"Retrying {exception.GetType().Name} ({_totalFailures}) - {StackTrace()}");
                return true;
            }

            if (exception is SqlException sqlException)
            {
                foreach (SqlError err in sqlException.Errors)
                {
                    // Enumerate through all errors found in the exception.
                    if (Enum.IsDefined(typeof(RetryableSqlErrors),err.Number))
                    {
                        _totalFailures++;
                        log.Info($"Retrying {exception.GetType().Name},{(RetryableSqlErrors)err.Number} ({_totalFailures}) - {StackTrace()}");
                        return true;
                    }
                }
            }

            log.Error($"Not retrying {exception.GetType().Name} - {StackTrace()}");
            return false;
        }
    }
}

设置:

using System.Data.Entity;
using MyDataModel.Extensions;

namespace MyDataModel
{
    internal class EntityFrameworkConfiguration : DbConfiguration
    {
        public EntityFrameworkConfiguration()
        {
            SetExecutionStrategy("System.Data.SqlClient",() => new CustomExecutionStrategy(Setting.MaxRetry,Setting.ShortWait));
        }
    }
}

然后,在App.Config中:

<entityFramework codeConfigurationType="MyDataModel.EntityFrameworkConfiguration,MyDataModel">
.
.
.
</entityFramework>

以下是一些日志摘录:

2020-08-11 04:09:15,047 [54] [26390536] ERROR MyDataModel.CustomExecutionStrategy - Not retrying SqlException - <>c__DisplayClass61_1.<FixItemAndRetry>b__1->BaseEntity.FixItemAndRetry...
2020-08-11 04:12:02,510 [52] [26557999] ERROR MyDataModel.CustomExecutionStrategy - Not retrying SqlException - <>c__DisplayClass61_1.<FixItemAndRetry>b__1->BaseEntity.FixItemAndRetry...
2020-08-11 11:09:53,350 [29] [3010774] INFO  MyDataModel.CustomExecutionStrategy - Retrying SqlException,DeadlockVictim (1) - Invoice..ctor->SyncInvoiceWithPayment.Start...
2020-08-11 11:56:12,047 [3] [5789470] INFO  MyDataModel.CustomExecutionStrategy - Retrying SqlException,DeadlockVictim (1) - Invoice..ctor->D365SyncInvoiceWorker.Start...
2020-08-11 11:56:17,048 [3] [5794471] INFO  MyDataModel.CustomExecutionStrategy - Retrying SqlException,DeadlockVictim (2) - Invoice..ctor->D365SyncInvoiceWorker.Start...
2020-08-11 14:16:20,111 [25] [3930388] INFO  MyDataModel.CustomExecutionStrategy - Retrying SqlException,DeadlockVictim (1) - Invoice..ctor->SyncInvoiceWithPayment.Start...
2020-08-11 14:16:25,110 [25] [3935386] INFO  MyDataModel.CustomExecutionStrategy - Retrying SqlException,DeadlockVictim (2) - Invoice..ctor->SyncInvoiceWithPayment.Start...
2020-08-11 14:40:35,089 [13] [5385366] INFO  MyDataModel.CustomExecutionStrategy - Retrying SqlException,DeadlockVictim (1) - Invoice..ctor->SyncInvoiceWithPayment.Start...
2020-08-11 14:40:40,089 [13] [5390365] INFO  MyDataModel.CustomExecutionStrategy - Retrying SqlException,DeadlockVictim (2) - Invoice..ctor->SyncInvoiceWithPayment.Start...
2020-08-11 14:58:51,459 [20] [6481736] INFO  MyDataModel.CustomExecutionStrategy - Retrying SqlException,DeadlockVictim (1) - Invoice..ctor->SyncInvoiceWithPayment.Start...
2020-08-11 14:58:53,958 [20] [6484234] INFO  MyDataModel.CustomExecutionStrategy - Retrying SqlException,DeadlockVictim (2) - Invoice..ctor->SyncInvoiceWithPayment.Start...

所以我知道自定义执行策略正在被调用,并且正在重试一些死锁。

但是从日志中,我有:

2020-08-11 11:09:46,783 [26] [3004206] INFO  Utility.Settlement - Getting invoice lines
2020-08-11 11:09:48,352 [26] [3005775] ERROR Utility.Settlement - Stl: <N0675833635639> Save Failed !
Error: An error occurred while reading from the store provider's data reader. See the inner exception for details.
InnerError: Transaction (Process ID 409) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

根据代码并解释错误消息,尝试从数据库中查询记录时会发生这种情况。

如何拦截EF6(6.4.4版)查询并使其重试这些SQL死锁?

解决方法

也许您超出了 MaxRetry 的设置。

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 &lt;select id=&quot;xxx&quot;&gt; SELECT di.id, di.name, di.work_type, di.updated... &lt;where&gt; &lt;if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 &lt;property name=&quot;dynamic.classpath&quot; value=&quot;tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-