views:

177

answers:

1

What happens when I save a change to web.config while the application is live? The reason I ask is that I'm working on a site/webapp right now which is built on top of an e-commerce platform. At seemingly random intervals, the site will stop responding. The process for the app pool is normal (no ridiculous memory or CPU usage when this happens). When I make a small change to web.config--such as adding a space or deleting a space, and then saving--the site seems to come back. I think by learning more about the sequence of events AFTER the save, I can narrow down the potential causes of my problem.

Edit: I should mention we're running on IIS 6.

+2  A: 

This is the expected behavior. The AppDomain it's running on ceases to take new work, and a new one is started.

John Saunders
So you think perhaps something in the AppDomain is causing the site to become unresponsive? I'm just wondering why I'm seeing no high CPU usage or memory usage, yet the site won't respond at all until a change is made to web.config.
Chris
"Something in the AppDomain" - _everything_ is in the AppDomain. All the code. All the data. So, yes, "something in the AppDomain" is breaking.
John Saunders
Great, that narrows it down.
Chris
I'd say that if recycling the appdomain fixes your app, something in your app is getting hung up or not responding.
Joe