Home > Blockchain >  What are common reasons of immediately recycling of application pool in IIS using ASP.Net MVC?
What are common reasons of immediately recycling of application pool in IIS using ASP.Net MVC?

Time:12-28

I have uploaded an application to hosting, but its application pools is recycling immediately after logging in, while its is working fine on local IIS. Any common reason facing this scenario?

I need to know What are common reasons of immediately recycling of application pool in IIS using ASP.Net MVC?

CodePudding user response:

iis app pool recycles on iis config file changes or based on the settings in IIS like Number of requests, memory limit, idle time, or scheduled restart. you an check the login time and event vower logs to find out why is app pool is recycling. generally is app poll does not recycle on the user login.

CodePudding user response:

Two different effects:

  • The AppPool process is the host for potentially multiple AppDomains. Typically this can be recycled by a number of effects. These could be time (every n hours), lack of requests, memory use and etc. all configured in IIS Config Manager.

  • The AppDomain, the hosted instance of your application root, can be
    cycled more frequently without affecting other AppDomains in the
    AppPool. Tess's post on AppDomain recycling is pretty insightful.

You are writing to a folder monitored for recompilation. This will trigger the AppDomain recreation at some point.

The event log will help you determine what cause initiated the recycle.

  • Related