5 Answer(s)

• 

  0

  berkansasmaz created one month ago

  Support Team .NET Developer

  Hello,

  Do you see the request twice when you use the ABP DataGrid etc. instead of KendoUI or the request manually from Swagger? When I search the datagrid of Kendo UI on the internet, I think that this is due to the filter of KendoUI's datagrid.

  See more:

  • https://www.telerik.com/forums/kendo-grid-filter-posting-twice
  • https://stackoverflow.com/questions/24068047/kendo-grid-making-duplicate-api-calls
  • https://www.google.com/search?q=Kendo+grid+make+request+twice&oq=Kendo+grid+make+request+twice&gs_lcrp=EgZjaHJvbWUyCwgAEEUYChg5GKABMgkIARAhGAoYoAHSAQg3NDA5ajBqMagCALACAA&sourceid=chrome&ie=UTF-8

  At first glance, I don't think it's ABP problem, so I want to make sure it's not KendoUI problem, so what have you done to test that it's not Kendo issue?

  Save Cancel
• 

  0

  kfrancis@clinicalsupportsystems.com created one month ago

  I'm 99% certain it has nothing to do with the actual client control (kendo). It's making a single call to the API, then the app service portion is being repeatedly called.

  I only see a single rest call to the page handler, which is pending the entire time that I get stopped multiple times at the app service layer.

  Save Cancel
• 

  0

  berkansasmaz created one month ago

  Support Team .NET Developer

  Hi,

  If it is possible, can you send your solution to support@abp.io email address (with the ticket number - #9325). Regards.

  Save Cancel
• 

  0

  kfrancis@clinicalsupportsystems.com created one month ago

  It appears to be an issue with Aspire and ABP. Now that I'm pretty sure this is the issue, I'll be able to fix up my repro and send that to you.

  Alternatively, your sample should have the same exact issue. The easiest way to see this is to have something in web call an app service where you either intentionally or unintentionally have code that takes long, like adding await Task.Delay(TimeSpan.FromSeconds(30)); - then you should see the exact same issue.

  Once I understood where the Polly retry was being caused, I was able to modify the AddServiceDefaults() extension method like so:

  public static TBuilder AddServiceDefaults<TBuilder>(this TBuilder builder) where TBuilder : IHostApplicationBuilder
  {
      builder.ConfigureOpenTelemetry();
  
      builder.AddDefaultHealthChecks();
  
      builder.Services.AddServiceDiscovery();
  
      builder.Services.ConfigureHttpClientDefaults(http =>
      {
          // Turn on resilience by default
          http.AddStandardResilienceHandler(resilience =>
          {
              // Set timeouts
              resilience.AttemptTimeout.Timeout = TimeSpan.FromMinutes(2);
              resilience.TotalRequestTimeout.Timeout = TimeSpan.FromMinutes(5); // Must be > attempt timeout
  
              // Configure retry (either set to 1+ or disable the strategy)
              resilience.Retry.MaxRetryAttempts = 1; // Minimum allowed value
  
              // Configure circuit breaker
              resilience.CircuitBreaker.SamplingDuration = TimeSpan.FromMinutes(5); // Must be ≥ 2× attempt timeout
          });
  
          // Turn on service discovery by default
          http.AddServiceDiscovery();
      });
  
      // Uncomment the following to restrict the allowed schemes for service discovery.
      // builder.Services.Configure<ServiceDiscoveryOptions>(options =>
      // {
      //     options.AllowedSchemes = ["https"];
      // });
  
      return builder;
  }
  

  Specifically, the section AddStandardResilienceHandler is what needed to be modified.

  Web Log: [2025-05-27 16:36:40.353] [Warning] () <CabMD.Web.Pages.Files.EdtIndexModel> === PAGE HANDLER START === [2025-05-27 16:36:40.354] [Warning] () <CabMD.Web.Pages.Files.EdtIndexModel> CorrelationId: "66a388fe", Time: 16:36:40.354 [2025-05-27 16:36:40.354] [Warning] () <CabMD.Web.Pages.Files.EdtIndexModel> Request: Page=1, PageSize=10, Skip=0 [2025-05-27 16:37:10.917] [Warning] () <CabMD.Web.Pages.Files.EdtIndexModel> === PAGE HANDLER END === [2025-05-27 16:37:10.917] [Warning] () <CabMD.Web.Pages.Files.EdtIndexModel> CorrelationId: "66a388fe", ResultCount: 10 [2025-05-27 16:37:10.935] [Warning] () <CabMD.PerformanceDiagnosticMiddleware> Slow request: "POST" "/Files/Edt" ("files/edt") took 30798ms (exceeds tolerable threshold of 500ms) [Status: 200]

  API Log: [2025-05-27 16:36:40.733] [Warning] () <CabMD.Controllers.Edt.EdtFileController> === API CONTROLLER START === [2025-05-27 16:36:40.733] [Warning] () <CabMD.Controllers.Edt.EdtFileController> RequestId: "6eca2ca5", Time: 16:36:40.733 [2025-05-27 16:36:40.734] [Warning] () <CabMD.Controllers.Edt.EdtFileController> HttpContext.TraceIdentifier: "0HNCTBOB4A9NI:00000026" [2025-05-27 16:36:40.734] [Warning] () <CabMD.Controllers.Edt.EdtFileController> Input: Skip=0, Max=10, Sorting=null [2025-05-27 16:36:40.736] [Warning] () <CabMD.Controllers.Edt.EdtFileController> Headers: "X-Requested-With=XMLHttpRequest" [2025-05-27 16:36:40.745] [Warning] () <CabMD.Edt.EdtFileAppService> === APP SERVICE START === [2025-05-27 16:36:40.745] [Warning] () <CabMD.Edt.EdtFileAppService> RequestId: "dfc9379f", CorrelationId: "no-correlation", Time: 16:36:40.745 [2025-05-27 16:36:40.745] [Warning] () <CabMD.Edt.EdtFileAppService> Method: "CabMD.Edt.EdtFileAppService".GetListAsync, Hash: 42651975 [2025-05-27 16:36:40.745] [Warning] () <CabMD.Edt.EdtFileAppService> Is Proxy: False [2025-05-27 16:36:40.745] [Warning] () <CabMD.Edt.EdtFileAppService> UOW ID: d451c0ca-00d6-4aeb-91d5-e175cf90ddf5, UOW IsActive: True [2025-05-27 16:36:40.745] [Warning] () <CabMD.Edt.EdtFileAppService> Input: Skip=0, Max=10 [2025-05-27 16:36:40.749] [Warning] () <CabMD.Edt.EdtFileAppService> Call Stack: "<GetListAsync>d__13.MoveNext -> AsyncMethodBuilderCore.Start -> EdtFileAppService.GetListAsync -> IReadOnlyAppService4_GetListAsync_7.InvokeMethodOnTarget -> AbstractInvocation.Proceed -> ProceedInfo.Invoke -> <ProceedAsynchronous>d__141.MoveNext -> AsyncMethodBuilderCore.Start -> AsyncInterceptorBase.ProceedAsynchronous -> <ProceedAsync>d__7.MoveNext" [2025-05-27 16:37:10.831] [Warning] () <CabMD.Controllers.Edt.EdtFileController> === API CONTROLLER END === [2025-05-27 16:37:10.832] [Warning] () <CabMD.Controllers.Edt.EdtFileController> RequestId: "6eca2ca5", ResultCount: 10

  Generally, in the host apps - there is something similar to the following:

  Log.Information("Starting web host.");
  var builder = WebApplication.CreateBuilder(args);
  
  builder.AddRedisClient("redis");
  builder.AddRedisDistributedCache("redis");
  
  builder.AddServiceDefaults(); // Bam, issue - if this is the default AddServiceDefaults and nothing modifies the resiliancy
  

  Save Cancel
• 

  0

  berkansasmaz created one month ago

  Support Team .NET Developer

  Hi,

  First of all, thank you very much for the information you have provided.

  .NET Aspire provides opinionated templates. In the article, the ServiceDefaults project is created using dotnet commands without any additional customization. Since these templates are opinionated, some configurations—such as retry timeout durations—are pre-configured based on common scenarios.

  However, these default settings may not suit your specific needs or certain endpoints. In such cases, you should customize the configuration accordingly. For instance, if you have non-idempotent methods, you might want to disable the retry mechanism altogether.

  You can also disable retries specifically for POST methods using the following configuration:

  httpClientBuilder.AddStandardResilienceHandler(options =>
  {
      options.Retry.DisableFor(HttpMethod.Post);
  });
  

  For more information: https://learn.microsoft.com/en-us/dotnet/core/resilience/http-resilience?tabs=dotnet-cli#disable-retries-for-a-given-list-of-http-methods

  I highly recommend reading this article on how you can fine-tune it: https://aws.amazon.com/builders-library/timeouts-retries-and-backoff-with-jitter

  Save Cancel