Attention: We are retiring the ASP.NET Community Blogs. Learn more >

The torture of the application recycle

I always read about this kind of thing, but can't imagine why anyone has the problem. Right now, it's happening to my current employer's test box.

The ASP.NET process is recycling frequently and seemingly at random. We can't figure out why. However, we did fire up the new health monitoring code in our web.config, and the app restarted because, it said, the "configuration changed."

Well, that certainly qualifies as one of the reasons an app will restart, but no one is molesting any configuration. Any theories?

4 Comments

  • I had the same problem (recycling 4 or 5 times a day). I was in a shared hosting environment so I blamed that. I ended up putting session into sql server so the users wouldn't be effected until I could move the code.



    When I finally did get to a dedicated server, same code mind you, it stopped recycling.



  • Could be some virus software that is touching those files. Filemon might help http://www.sysinternals.com/Utilities/Filemon.html

  • Could also be the indexing service.

  • I second Raj's FileMon suggestion. If anything is constantly touching the config file FileMon will reveal the offending process. If that's not it you should look at memory usage. .NET will dump and restart due to memory pressure.

Comments have been disabled for this content.