ASP.net 2.0

[Mike]

What conditions cause a web application to restart? Essentially losing
session state?
--
MikeG

[Dot Net Jose]

I don't know all of them, but I know that the worker process is
scheduled to restart on an interval if it goes on an Idle status.
Check out the ASP.net settings in the IIS properties to findout what
the number is.

Another is when the Web.config file changes.

Hope that helps.

[V]

Hi,

Found this on the internet:
http://www.dotnetindia.com/2003/10/why_aspnet_rest.html

Copying from there:

- The max compilation limit is reached (look for
numRecompilesBeforeApprestart in machine.config)
- Physical application path of the web application has changed.
- Change in global.asax or one of the included files
- Change in machine.config
- Change in web.config in the app root
- Change inside bin directory or its subdirs
- A directory is renamed to bin, or bin is created
- Overwhelming change notifications - too many files are changed too
fast in one of content directories - could happen if, for example,
files are generated on the fly per request
- Change in the code-access security policy file
- User code called HttpRuntime.UnloadAppDomain
- Any directory under the web application folder is renamed

Regards,
Vaibhav
www.nagarro.com

[Rajesh CKR]

It could be for varity of reasons .. Like, application pool setting asking
it to recycle every x interval, or, when the memory used reaches a specific
limit, or some fault in the application itself - like stack overflow etc...

You may have to check your application for memory leaks. But an immediate
fix for not loosing the session state is to use stateful sessions against
databases...

HTH

Rajesh CKR

"Mike" <Mi**@discussions.microsoft.com> wrote in message
news:AC**********************************@microsof t.com...

What conditions cause a web application to restart? Essentially losing
session state?
--
MikeG

[Cowboy \(Gregory A. Beamer\)]

There are some configurable items, as mentioned by Dot Net Jose. There is
also the possibility of crashing the worker process with bad code. If the
app is randomly rebooting during usage, it is most likely your code. Find
out what exceptions are thrown at the time and correct them.

Possibilities

Out of stack space

Out of memory

Unsafe code

Etc.
--
Gregory A. Beamer

*************************************************
Think Outside the Box!
*************************************************
"Mike" <Mi**@discussions.microsoft.com> wrote in message
news:AC**********************************@microsof t.com...

What conditions cause a web application to restart? Essentially losing
session state?
--
MikeG

[Mike]

that article does not mention asp.net 2.0...only asp.net 1.*
--
MikeG
"V" wrote:

Hi,

Found this on the internet:
http://www.dotnetindia.com/2003/10/why_aspnet_rest.html

Copying from there:

- The max compilation limit is reached (look for
numRecompilesBeforeApprestart in machine.config)
- Physical application path of the web application has changed.
- Change in global.asax or one of the included files
- Change in machine.config
- Change in web.config in the app root
- Change inside bin directory or its subdirs
- A directory is renamed to bin, or bin is created
- Overwhelming change notifications - too many files are changed too
fast in one of content directories - could happen if, for example,
files are generated on the fly per request
- Change in the code-access security policy file
- User code called HttpRuntime.UnloadAppDomain
- Any directory under the web application folder is renamed

Regards,
Vaibhav
www.nagarro.com

[Juan T. Llibre]

Everything the article states is also valid for 2.0, not just for 1.1.

Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Mike" <Mi**@discussions.microsoft.com> wrote in message
news:DA**********************************@microsof t.com...

that article does not mention asp.net 2.0...only asp.net 1.*
--
MikeG
"V" wrote:

Hi,

Found this on the internet:
http://www.dotnetindia.com/2003/10/why_aspnet_rest.html

Copying from there:

- The max compilation limit is reached (look for
numRecompilesBeforeApprestart in machine.config)
- Physical application path of the web application has changed.
- Change in global.asax or one of the included files
- Change in machine.config
- Change in web.config in the app root
- Change inside bin directory or its subdirs
- A directory is renamed to bin, or bin is created
- Overwhelming change notifications - too many files are changed too
fast in one of content directories - could happen if, for example,
files are generated on the fly per request
- Change in the code-access security policy file
- User code called HttpRuntime.UnloadAppDomain
- Any directory under the web application folder is renamed

Regards,
Vaibhav
www.nagarro.com

[Jose Fernandez]

one question. My applications built in framework inferior to 2.0, are able
to run in a server with this version?
"Mike" <Mi**@discussions.microsoft.com> wrote in message
news:DA**********************************@microsof t.com...

that article does not mention asp.net 2.0...only asp.net 1.*
--
MikeG
"V" wrote:

Hi,

Found this on the internet:
http://www.dotnetindia.com/2003/10/why_aspnet_rest.html

Copying from there:

- The max compilation limit is reached (look for
numRecompilesBeforeApprestart in machine.config)
- Physical application path of the web application has changed.
- Change in global.asax or one of the included files
- Change in machine.config
- Change in web.config in the app root
- Change inside bin directory or its subdirs
- A directory is renamed to bin, or bin is created
- Overwhelming change notifications - too many files are changed too
fast in one of content directories - could happen if, for example,
files are generated on the fly per request
- Change in the code-access security policy file
- User code called HttpRuntime.UnloadAppDomain
- Any directory under the web application folder is renamed

Regards,
Vaibhav
www.nagarro.com