Base solution for your next web application
Open Closed

Backend Application Many crashes #9898


User avatar
0
kobaid created
  • product version : 6.9.0.0
  • product type : Angular
  • product framework type : .net core

We have an application for customer which is built on ASPZero and running in production since 2019. The application is deployed on three servers (front-end, back-end and database). We are struggling to solve an issue started since go-live. The back-end server pool (IIS application pool) is crashing frequently with no obvious reason. The only way to resume the application is to recycle the back-end IIS pool. This crash is happening from time to time, it happens daily once or twice if we have users accessing and updating the application. However, sometimes it disappear for over a week when there are no visitors. We tried almost all scenarios to simulate the issue with no luck. Currently we started to use stress tools, such as JMeter to simulate multi users in order to bring the portal down as usual with no luck as well. When the crash happened before, we couldn’t find any trace in any of the servers log neither the application logs. Latest hope is to prepare for IIS dump and wait for the issue to appear in order to capture the IIS dump and analyze it.

Finally, our challenge in this case is to simulate the issue (make it happen) as we know it’s there but due to no user visits we couldn’t have it again. Second challenge is to identify the root cause of this issue when it’s occur and solve it.

Below, please find further details about the application:

App Deployment: 3 tiers deployed on three separate servers (Front, Back, Database) Environment: Virtual hosting on windows servers 2016, SQL Server 2017. Security: WAF layer, End point security on all servers (ESet enterprise antivirus) Multi-Tenant: Enabled (218 Tenants)

kindly you support concerns above


10 Answer(s)
  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi @kobaid

    As you stated it is hard to detect such problems but there are some obvious reasons which can cause this problem in specific cases. First, could you check if you have any async void method in your application ?

  • User Avatar
    0
    kobaid created

    Dear ismcagdas,

    Thank you for your prompt reply, We have searched the whole solution and didn’t find any usage for (async void method). We in fact are using (async Task ).

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi @kobaid

    Could you also share your;

    1. Abp Nuget packge version
    2. .NET Core version you are using ?

    Thanks,

  • User Avatar
    0
    kobaid created

    Hi ismcagdas,

    We using Abp with 4.5.0 And using .net core 2.2

    Regards

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi,

    Could you upgrade your ABP version to latest 4.20.0 and try this again ?

  • User Avatar
    0
    kobaid created

    hi ismcagdas,

    Do you mean to upgrade all nugets backages start with Abp like(Abp.AspNetCore) or only Abp? I am assuming you meant Abp only. i will update it and let you know. the challange is finding the result, if the problem is solved or not. becuase currently it is disapeared and we couldn't simulate it again.

    Regards

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi @kobaid

    I mean all packages starting with Abp prefix. Abp.AspNetCore must be updated as well. If you only update Abp package, you will face problems.

  • User Avatar
    0
    sedulen created

    @kobaid - were you able to resolve your issue? We are also running an older version of the framework (Abp with 4.5.0 & .net core 2.2).

    We have looked into upgrading to dotnet core 3.1 or dotnet core 5.0, but the upgrade effort has been quite significant, so I'm considering @ismcagdas' suggestion of upgrading to Abp 4.20.0

    Thanks, -Brian

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi @sedulen

    I have made a suggestion to you in another topic.

  • User Avatar
    0
    kobaid created

    Dear @sedulen,

    Thank you so much, It was too late when we start the solution. the issue was fatal to customer. anyway, good luck to you.