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.


Comments

  1. AnonymousMay 31, 2013 at 2:45 PM

    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

    ReplyDelete

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 above When 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 implementa...
4 comments
Read more

Finalization, Know What it Costs

This is a post about object finalization in .NET. Finalization is not as inexpensive as we think, it increases the pressure put on GC.All objects that need finalization are moved into a finalizable queue and the actual finalization happens in a separate thread. Because the objects full state may be needed, the object itself and all the object it points to are promoted to the next generation (this is needed so that GC does not clean these objects off in the current round), and these objects are cleaned up only after the following GC. Due to this reason, resources that need to be released should be wrapped in as small a finalizable object as possible, for instance if your class needs a reference to an unmanaged resource, then you should wrap the unmanaged resource in a separate finalizable class and make that a member of your class and furthermore the parent should be a non-finalizable class. This approach will assure that only the wrapped class (class that contains the unmanaged resourc...
1 comment
Read more

The maximum nametable character count quota (16384) has been exceeded

Some of our services were growing and the other day it hit the quote, I could not update the service references, nor was I able to run the WCFTest client. An error is diplayed saying " The maximum nametable character count quota (16384) has been exceeded " The problem was with the mex endpoint, where the XML that was sent was too much for the client to handle, this can be fixed by do the following. Just paste the lines below within the configuration section of the devenve.exe.config and the svcutil.exe.config files found at the locations C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE , C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin Restart IIS and you are done. The detailed error that you get is the following : Error: Cannot obtain Metadata from net.tcp://localhost:8731/ Services/SecurityManager/mex If this is a Windows (R) Communication Foundation service to which you have access, please check that you have enabled metadata publishing at the specified address. F...
5 comments
Read more