Skip to main content

IIS Worker Process Quits, Service Unavailable

Ran into one of those issue yesterday that I have come across almost 2 years back. My WCF service was hosted on IIS, and we were doing a few load tests, after a few rounds of requests no request went through and was in error.
Tried browsing the WCF SVC file from IIS and got the message "Service Unavailable", went to the application pool section in IIS and noticed that the app pool running the WCF service has stopped.
In a situation like this, I never try to just fix the issue but to see why the problem has come in the first place.
Took a look at the event viewer and I could see a number of errors from ASP.NET and that the worker processor has quit.
Took a look at the code and the code pointed out that their was a piece of code that runs on a separate thread and that thread throws an error due to a missing stored procedure in the database.

So why does the worker processor stop when there is an error?, by default, from .NET 2.0, if there is an unhandled exception, the worker processor quits, but only if this exception is thrown from a thread that does not service the request. If an unhandled exception is thrown from the thread that services the request then its is thrown as a exception to the user.
However, if the exception is thrown from a thread not part of the thread that service the request then it will quit the worker processor.

Any the reason as per Microsoft for this behavior "We do not recommend that you change the default behavior. If you ignore exceptions, the application may leak resources and abandon locks"

So watch out, if you are spawning thread from the ASP.NET request, make sure to handle exception within the thread and log it.


  1. Your style is unique in comparison to other people
    I've read stuff from. I appreciate you for posting when you have the opportunity, Guess I will just bookmark this web site.

    Feel free to surf to my page; summer internship


Post a Comment

Popular posts from this blog

Hosting WCF services on IIS or Windows Services?

There came one of those questions from the client whether to use II7 hosting or windows service hosting for WCF services. I tried recollecting a few points and thought of writing it down.
WCF applications can be hosted in 2 main ways- In a Windows service- On IIS 7 and aboveWhen WCF was first released, IIS 6 did not support hosting WCF applications that support Non-HTTP communication like Net.TCP or Net.MSMQ and developers had to rely on hosting these services on Windows Services.With the release of IIS 7, it was possible to deploy these Non-Http based applications also on IIS 7. Following are the benefits of using IIS 7 to host WCF applications
Less development effort
Hosting on Windows service, mandates the creating of a Windows service installer project on windows service and writing code to instantiate the service, whereas the service could just be hosted on IIS by creating an application on IIS, no further development is needed, just the service implementation is n…

Task based Asynchronous pattern, Async & Await and .NET 4.5

One of the key features in .Net 4.5 is to write asynchronous programs much easier. So if I was to write asynchronous programs in .Net 2.0/3.5, I would either follow the event based model or the callback based model. For an example, a synchronous method that does intensive work (say the DoWork()) can be made asynchronous by using the following patterns
1) Implementing the IAsyncResult pattern. in this implementation, 2 methods are exposed for the DoWork() synchronous method, the BeginDoWork() and the EndDoWork() method. The user will call the BeingDoWork() passing in the required parameters and a callback of the delegate type AsyncCallback(IAsyncResult). The BeginDoWork() will spawn a new thread a return control back to the user. Once work is completed in the spawned method, as a last step, it will call the inform the AsyncResult implementation, which in turns will call the EndDoWork() (which is the callback that was passed in to the BeginDoWork()).
2) Implementing the event pattern. Her…

MEF (Managed Extensibility Framework), .NET 4, Dependency Injection and Plug-in Development

Almost after .Net 4 was released I remember reading about MEF (Managed Extensibility Framework), this was a framework for developers to compose their application with required dependencies. At first this looks like the Unity Container used for dependency injection, but MEF is much more than a dependency container but there is nothing stopping you from using MEF as a dependency injector.I remember around 5 years back when I was in a project that created a framework that allows developers to plug-in there modules as WinForm screens. The developer would create a set of screens with the intended functionalities and the drop this component in the bin folder of the framework and then will move on to do some painful configurations for the framework to pick up the module. Dropping the component into the bin folder and doing a bit of configuration is all that s needed for the framework to pick up display the screens. Typically, the configurations would also contain metadata about the screen.Al…