I have asp.net mvc intranet site that is deployed to IIS6. Site is used rarely so app pool tends to shutdown. When user click the page for the very first time 5-10 seconds are passed till page appears (app pool started and site is compiled). Situation repeats for the next page and so on. AFAIK IIS7 has option to disable App pool shutdown but IIS6 lacks it.
Nowadays i have special utility that pings site periodically (10 pages) in order to determine if pages are available and keeps site always ready for users this way.
Is it normal or may be I've missed something in IIS6 configuration? Do you use such pinger apps in production to notify support/admins if site is not available?
Thank you in advance!
You can disable application pool shutdowns on IIS 6.
Related
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?
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.
I have an IIS server hosting 40-50 ASP.Net MVC websites.
Each website has its own ApplicationPool.
When I need to restart the server for updates or config changes it takes about 3 hours for IIS to startup again. If I change each appPool to not Start Immediately IIS starts as normal and I have to go through each appPool to start them up manually. Which is a pain but it is faster.
Any Ideas why these AppPools should be taking so long to startup?
Regards
Carl
I have a Azure website consisting of a WCF endpoint and a MVC website running on Azure. It runs on a basic medium/large tier - so no cap in CPU as Free or Basic has. This has been running perfectly for 6 months probably, with regular deployments and updates. And performance has as expected kept consistent. But now suddenly it takes forever to load the MVC website.
The flow is as follows; we receive a call via the WCF endpoint and then we direct people to a URL that is the MVC web site. All resides on same "web site" inside Azure.
The strange thing is that I can see no difference in my log files. The WCF endpoint responds as quickly as always and from what I can see the heavy lifting inside the MVC also responds as expected, but still the user is left waiting forever on the specified URL?
As said I can't see anything in the performance logs for the MVC controllers, so somehow it seems to be the https request itself that takes ages, but how do I debug or measure this?
I am in the process of getting Visual Studio 2015 to see the remote profiling that can be generated through KUDO - but somehow I don't think that the problems resides here. I am kind of blanking so any thoughts on what could be wrong and how to debug would be appreciated. Also if anyone knows that Azure has released something within the last couple of weeks that might have slowed the application down.
Any chance that you have Application Insights turned on for the MVC site? It has a feature that will track dependency calls and should be able to give you a good idea of what is taking a long time.
https://azure.microsoft.com/en-us/documentation/articles/app-insights-asp-net-dependencies/
I'm seeing a really strange behavior in one of my applications. It is an ASP.NET MVC application, running in IIS7. I have a very small bit of code that is running out of the context of any request (think of a basic heartbeat over a TCP socket). However, I notice that when there is no activity, the heartbeat seems to stop. If I simply make a request against the site, everything is peachy again.
So, my question is, what is the expected behavior of code running outside of any request context?
By default, IIS application pools will stop after 20 minutes of inactivity.
Configure Idle Time-out Settings for an Application Pool (IIS 7)
I wonder how long will an ASP.NET (MVC) application run, when no new requests come in? Lets say I'm using an IOC Container ans have a Singleton Object serving to the clients. As far as I know it will serve different page requests. But how long will it live when no new request come in? Is there any timeout (maybe configured through IIS) that says when my app will shut down?
Typically it will run for 20 min because that is the default value for IIS7. You can configure that value, however.