W
woolley.dean
The problem we are having is with the worker process restarting after
one minute of being started up. We had a website running in .Net 1.1
and switched it over to .Net 2.0. The site is running on a W2003
machine w/ IIS6 with 4GB Ram.
We have it running in it's own Application Pool with no other websites.
The settings we have are:
- Recycle worker process after 1440 Minutes
- Shut down worker proecess after being idle for 20 minutes
- Enable pinging = false
- Enable Rapid Fail Protection = false
I'm looking for any direction to look/try.
I have tried making a minimal asp .net website (just one page that does
a Response.Write("")) with the default settings in web.config and the
worker process does not restart. If I move over the web.config from
the problem site to the test site, the worker process will react in the
same manner by restarting after approximately one minute. There is no
traffic during this period. I basically hit the site once, and let the
worker process start. Then I wait, and 100% of the time it will
restart. I know it is not a problem with memory are doing this will
only use about 20MB of Ram.
I have tried removing sections from the web.config until it is down to
the least amount of information I can and it still restarts.
Here is what I have when I say "least amount of information" in
web.config.
<?xml version="1.0"?>
<configuration>
<appSettings>
</appSettings>
<system.web>
<httpModules>
<compilation debug="false">
</compilation>
<customErrors mode="Off"/>
<authentication mode="Windows">
</authentication>
</system.web>
</configuration>
Any help is appreciated
one minute of being started up. We had a website running in .Net 1.1
and switched it over to .Net 2.0. The site is running on a W2003
machine w/ IIS6 with 4GB Ram.
We have it running in it's own Application Pool with no other websites.
The settings we have are:
- Recycle worker process after 1440 Minutes
- Shut down worker proecess after being idle for 20 minutes
- Enable pinging = false
- Enable Rapid Fail Protection = false
I'm looking for any direction to look/try.
I have tried making a minimal asp .net website (just one page that does
a Response.Write("")) with the default settings in web.config and the
worker process does not restart. If I move over the web.config from
the problem site to the test site, the worker process will react in the
same manner by restarting after approximately one minute. There is no
traffic during this period. I basically hit the site once, and let the
worker process start. Then I wait, and 100% of the time it will
restart. I know it is not a problem with memory are doing this will
only use about 20MB of Ram.
I have tried removing sections from the web.config until it is down to
the least amount of information I can and it still restarts.
Here is what I have when I say "least amount of information" in
web.config.
<?xml version="1.0"?>
<configuration>
<appSettings>
</appSettings>
<system.web>
<httpModules>
<compilation debug="false">
</compilation>
<customErrors mode="Off"/>
<authentication mode="Windows">
</authentication>
</system.web>
</configuration>
Any help is appreciated