RE: AppDomain won't recycle on web.config change since 1.1 to 2.0
- From: Stefan Barlow <stefanbarlow@xxxxxxxxxxxxxxxx>
- Date: Thu, 8 Mar 2007 11:33:49 -0800
1) Correct, the DFS has been in use for these web sites for months.
2) All assemblies are in the GAC. We change the version numbers referenced
in the GAC on the web.config and save it.
3) Correct.
4) Correct. Does creating files / folders under a child folder cause this
as well?
All assemblies are in the GAC, we do not have a /bin folder.
Thanks,
--
Stefan Barlow
MCSD.Net
"Walter Wang [MSFT]" wrote:
Hi Stefan,.
Let me summarize the issue so far:
1) You have multiple web servers using a single DFS share (I believe you
already properly configured in IIS to use this DFS share since you need a
specific account to visit that DFS share)
2) Some assemblies used by your web application are installed in GAC; each
web server has auto-update system to update them in GAC and touch
web.config to cause the web application restart
3) This is previously working fine in ASP.NET 1.1; now you've upgraded to
ASP.NET 2.0 and you found touching web.config is not causing the web
application restart and even it did, some assembly will not load correctly
and only restaring the AppPool could solve the problem.
4) You also found that in ASP.NET 2.0, creating a folder in the web site's
root folder will cause the AppDomain restart and you're wondering if
uploading image files will cause it restart too.
Let me know if I've misunderstood or missed anything.
Well, previously in ASP.NET 1.1, touching web.config, global.asax and /bin
will cause AppDomain restart. Now since ASP.NET 2.0 has some special folder
such as App_Code, App_Data, it now will restart the AppDomain whenever a
folder is created/deleted under the root folder. This is by design in 2.0.
#If broken it is, fix it you should : ASP.NET Case Study: Lost session
variables and appdomain recycles
http://blogs.msdn.com/tess/archive/2006/08/02/asp-net-case-study-lost-sessio
n-variables-and-appdomain-recycles.aspx
I'm not sure why touching web.config didn't cause the AppDomain restart in
your case. As you described, adding a folder will cause it restart,
therefore the FileSystemWatcher (internally used by ASP.NET to detect
changes) should be working correctly. I'm afraid this is an environment
specific scenario that needs live debugging or dump analysis to further
troubleshoot the root cause, which is unfortunately not possible in
newsgroup.
From the fusion log you posted, the problematic assembly is located at your
/bin folder, right? Remeber that updating a file in /bin will cause the
AppDomain restart.
This issue might be related to the 1.1 to 2.0 migration. Have you tried to
create a brand new 2.0 web application following your deployment scenario
and update an assembly used?
At last, I highly recommend you to contact our Customer Support and Service
to fully troubleshooting this issue. With live debugging and dump analysis,
I believe the issue will be more easier and sooner to solve.
Regards,
Walter Wang (wawang@xxxxxxxxxxxxxxxxxxxx, remove 'online.')
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
- Follow-Ups:
- RE: AppDomain won't recycle on web.config change since 1.1 to 2.0
- From: Walter Wang [MSFT]
- RE: AppDomain won't recycle on web.config change since 1.1 to 2.0
- References:
- RE: AppDomain won't recycle on web.config change since 1.1 to 2.0 swit
- From: Walter Wang [MSFT]
- RE: AppDomain won't recycle on web.config change since 1.1 to 2.0
- From: Stefan Barlow
- RE: AppDomain won't recycle on web.config change since 1.1 to 2.0
- From: Walter Wang [MSFT]
- RE: AppDomain won't recycle on web.config change since 1.1 to 2.0
- From: Stefan Barlow
- RE: AppDomain won't recycle on web.config change since 1.1 to 2.0
- From: Walter Wang [MSFT]
- RE: AppDomain won't recycle on web.config change since 1.1 to 2.0 swit
- Prev by Date: Re: WebServer to host ASP.NET applications
- Next by Date: Re: Changing the 404 Page not found page.
- Previous by thread: RE: AppDomain won't recycle on web.config change since 1.1 to 2.0
- Next by thread: RE: AppDomain won't recycle on web.config change since 1.1 to 2.0
- Index(es):
Relevant Pages
|