We host aspx pages in remote virtual directories using a UNC path and I'm working on trying to harden IIS to not fall down if connectivity to the UNC path is lost. Using Process Monitor, I noticed that IIS 7 (on W2K8) with AppPool in .NET 4.0 and with contiuous load will check the UNC path about every 80 seconds. It does not do this if the file is local or the AppPool uses .NET 2.0. I can't find anything online that might explain this behavior and am hoping someone here on the forums might have some insight.
At first, I thought this may have had something to do with our application, but I was able to reproduce this issue with a dummy website and aspx page on my Windows 7 box. Steps to reproduce are:
1. Create a new application that uses an AppPool that uses .NET 4.0.
2. Create a virtual directory that points to a UNC path and put a simple helloworld.aspx page there.
<html><%=”Hello, World!” %></html>
2. Open up Process Monitor and filter on Process Name = w3wp.exe and Path ending with helloworld.aspx.
3. Open up a browser and go to the helloworld.aspx page and keep on refreshing. If you do this for 4 minutes, you should see w3wp.exe do file operations on the helloworld.aspx page about every 80 seconds.
Put the file locally or use .NET 2.0 and this doesn't happen. Does anybody have any insight to why this is happening? If not that, can anybody else reproduce this just to check my sanity? Thanks.