Consider enabling transient error resiliency by adding 'EnableRetryOnFailure()' to the 'UseSqlServer' call on ASP.NET core 2.2

Question

I'm using aspnetboilerplate solution developed with ASP.NET core 2.2 . The backend is deployed on azure and it uses the SQL server provided.

Sometimes, when the backend has a lot of requests to handle, it logs this exception:

Mvc.ExceptionHandling.AbpExceptionFilter - An exception has been raised that is likely due to a transient failure. Consider enabling transient error resiliency by adding 'EnableRetryOnFailure()' to the 'UseSqlServer' call. System.InvalidOperationException: An exception has been raised that is likely due to a transient failure. Consider enabling transient error resiliency by adding 'EnableRetryOnFailure()' to the 'UseSqlServer' call. ---> System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the serv

I tried to solve this problem adding this code to my Startup.cs

public IServiceProvider ConfigureServices(IServiceCollection services)
        {
            // MVC
            services.AddMvc(
                options => options.Filters.Add(new CorsAuthorizationFilterFactory(_defaultCorsPolicyName))
            ).AddJsonOptions(
            // To fix OldContract in Contract entity (self-referencing loop)

        services.AddDbContext<ManagerDbContext>(options =>
        {
            options.UseSqlServer(_appConfiguration["ConnectionStrings:Default"],
                sqlServerOptionsAction: builder =>
                {
                    builder.EnableRetryOnFailure(
                        maxRetryCount: 10,
                        maxRetryDelay: TimeSpan.FromSeconds(30),
                        errorNumbersToAdd: null);
                });
        });

    }

But the problem is not solved.

where do you build and deploy your project? Via Azure Pipelines or on your local machine? If you are using Azure Pipelines, please check if the problem also occurs when you try on local. — Bright Ran
– Bright Ran, Commented Dec 9, 2020 at 7:41
How are things going? Have you tried on your local? Does it work? Please try it, any progress, feel free to tell me. Thanks. — Bright Ran
– Bright Ran, Commented Dec 10, 2020 at 6:54
Yes sorry, i can't try it on my local environment because this appens only on azure when backend has a lot of requests (from a lot of users). And yes i use azure pipelines . I tried also to build locally and after deploy it manually on azure, but the problem occurs again. — C1X
– C1X, Commented Dec 11, 2020 at 12:09
I think it has mapping issue between the incoming request and the database object mapping. Hence transient error. — Abhijeet Sinha
– Abhijeet Sinha, Commented Dec 13, 2020 at 12:54

CinCout · Accepted Answer · 2022-12-15 17:58:15Z

0

you will have to add your error code in the list errorNumbersToAdd:

options.EnableRetryOnFailure(
        maxRetryCount: 3,
        maxRetryDelay: TimeSpan.FromSeconds(10),
        errorNumbersToAdd: new List<int> { Add your code here});

edited Dec 15, 2022 at 17:58

CinCout

9,62916 gold badges55 silver badges74 bronze badges

answered Dec 11, 2022 at 15:51

Keith Jairam

93 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Consider enabling transient error resiliency by adding 'EnableRetryOnFailure()' to the 'UseSqlServer' call on ASP.NET core 2.2

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related