Configuration for multiple ASP.Net Worker processes

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jeff Clausius - 02 Mar 2005 22:59 GMT

Does anyone know if it is possible to configure IIS 5.0 to run distinct
ASP.Net worker processes for each distinct Web Site?

For example, in IIS 6.0, you can create WebSite1, and WebSite2. Then
install two distinct ASP.Net apps under each web site. Once both
applications have been started, you will notice two distinct w3wp.exe
processes.

However, with IIS 5.0, the same configuration results in one single
aspnet_wp.exe process. Is it possible to make a change to either IIS or
the .Net framework to allow multiple aspnet_wp.exe processes to run?

Thanks
Jeff Clausius

Reply to this Message

Manohar Kamath - 02 Mar 2005 23:50 GMT

That's the limitation of IIS 5, you can't -- there is one worker process
with multiple threads servicing different app domains. Time to upgrade :)

Signature

Manohar Kamath
Editor, .netWire
www.dotnetwire.com

> Does anyone know if it is possible to configure IIS 5.0 to run distinct
> ASP.Net worker processes for each distinct Web Site?
[quoted text clipped - 10 lines]
> Thanks
> Jeff Clausius

Reply to this Message

Jeff Clausius - 03 Mar 2005 14:35 GMT

If all threads exist in one worker process, one bad apple can bring down
the entire worker process.

How does the IIS application isolation prevent this? Or does it?

> That's the limitation of IIS 5, you can't -- there is one worker process
> with multiple threads servicing different app domains. Time to upgrade :)

Reply to this Message

Manohar Kamath - 03 Mar 2005 15:45 GMT

From what I know, although there is one worker process, but requests are
processed on different threads. So, if a request in one thread gets bad, the
thread just exits with an error, with the aspnet_wp.exe still handling other
requests.

Also note that the IIS 5 application isolation applies to the app, and not
to ASP.NET in particular. Even in high-isolation mode, when apps are running
out of process of IIS, the requests to ASP.NET pages are still made to the
worker process.

Signature

Manohar Kamath
Editor, .netWire
www.dotnetwire.com

> If all threads exist in one worker process, one bad apple can bring down
> the entire worker process.
[quoted text clipped - 4 lines]
> > with multiple threads servicing different app domains. Time to upgrade
:)

Reply to this Message

Jeff Clausius - 04 Mar 2005 15:35 GMT

Great. Thanks for the explanation.

Jeff

> From what I know, although there is one worker process, but requests
> are processed on different threads. So, if a request in one thread
[quoted text clipped - 5 lines]
> are running out of process of IIS, the requests to ASP.NET pages are
> still made to the worker process.

Reply to this Message

Configuration for multiple ASP.Net Worker processes

Free Magazines