This WAS is reporting stuff in Windows Events, in the System log. Once the condition causing the crashes is removed, then the administrator may manually re-Start the application pool. So why don’t I stop doing that, marking the Application Pool accordingly (Stopped), until the administrator is fixing the cause. It is expensive for the system to create these processes, which crash anyway. I keep creating processes for this app, and they crash. But if these processes are repeatedly crashing, soon after being created, WAS is going to “say”: If a worker process crashes, WAS would immediately try to create a new process for the Application Pool because the Web apps needs to continue serving requests. These are the processes responding to HTTP requests. These are the IIS processes that are loading and then executing the Web apps, including the Asp.Net ones. You see, there is an IIS component called WAS, Windows (Process) Activation Service, that is creating and then monitoring the worker processes – w3wp.exe – for application pools. Img 1, Rapid-Fail Protection settings for an Application Poolīut why turning off the application pool at all? Why is IIS doing that? These values are the default values but you get the point. If the hosted application is causing the crash of its executing process for 5 times in less than 5 minutes, then the Application Pool is turned off automatically. In most of the cases, we have a 503.0, Application pool unavailable and when we check the corresponding application pool, it shows “ Stopped”.īelieve it or not, that is actually a feature in IIS acting: the Rapid-Fail Protection. If we’re looking at the reference list of responses that IIS could send, an HTTP response status 503 means Service Unavailable. In many cases, it may be needed to collect memory dumps to study the exceptions causing the crash: see article at. Evidence of what causes the w3wp.exe to crash may be found in Windows Events, in the Application log: second-chance crashing exceptions with w3wp.exe.Ĭollecting the IIS basic troubleshooting info helps expedite investigation for the root cause of application crashes.Evidence of repeated w3wp.exe crashes and Rapid-Fail Protection may be found in Windows Events, in the System log with Source=WAS.It helps prevent consuming valuable system resources creating a worker process that crashes anyway, soon after spawning. This is a feature of IIS, at Application Pool level, called Rapid-Fail Protection. Since the w3wp.exe worker process, created by IIS to execute a web application, is crashing frequently, the respective IIS application pool is turned off. The 503 response from the IIS machine, Service Unavailable, is the result of repeated application crashes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |