E
Eduardo Crivelli via DotNetMonster.com
Hi everybody,
I'm new to this site and regarding the quality of the threads I'm confident
that I will get some help here. Here is the case:
We have a huge asp.net c# (101 bins and more than 4.000 aspx)(.net
framework 1.0, latest sp) internet site in W2K plataform. And since last
week, every time someone deploys new pages or assemblies the site goes
made. It recycles every 10 to 20 minutes until you go and reboot the
machine.
Our deployment time uses this procedure:
- stop WWW.
- execute iisreset.
- clean C:\WINNT\Microsoft.NET\Framework\v1.0.3705\Temporary ASP.NET Files
- make the deploy (xcopy the files).
- start WWW.
Last Friday I managed to understand what was going on, they have misplaced
the files and created copies of the directories in wrong places and I think
..net had a hard time serving this application. However yesterday it started
recycling again and for my total surprise nothing seems to be wrong with
the site.
Our application saves logs in the event viewer like that for each recycle:
Event Type: Warning
Event Source: portal.WEB
Event Category: (200)
Event ID: 111
Date: 12/4/2005
Time: 10:49:00
User: N/A
Computer: CAUDES2KATIX
Description:
<ACALog><LogCategory>AppAudit</LogCategory><Header>ClientApplication -
Application End</Header><EventID>111</EventID><Body><Message>Finalizando
aplica??o:
at App.MCA.Global.Application_End(Object, EventArgs)
at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object,
BindingFlags, Binder, Object[], CultureInfo, Boolean, Assembly, Boolean)
at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object,
BindingFlags, Binder, Object[], CultureInfo, Boolean)
at System.Reflection.RuntimeMethodInfo.Invoke(Object, BindingFlags,
Binder, Object[], CultureInfo)
at System.Web.HttpApplication.ProcessSpecialRequest(HttpContext,
MethodInfo, Int32, Object, EventArgs, HttpSessionState)
at System.Web.HttpApplicationFactory.FireApplicationOnEnd()
at System.Web.HttpApplicationFactory.Dispose()
at System.Web.HttpRuntime.Dispose()
at System.Web.HttpRuntime.ReleaseResourcesAndUnloadAppDomain(Object)
</Message><Src>Global.Application_End</Src><contextItems
/></Body><Severity>2</Severity><MachineName>CAUDES2KATIX</MachineName><DateTime>12/4/2005
10:49:00</DateTime></ACALog>
Microsoft say that when you get ReleaseResourcesAndUnloadAppDomain() is
because you have changed something on the application's directory (bins,
web.config, machine.config, etc) and this is asp.net way to week itself up-
to-date.
We were supposed to get just one recycle per deployment and we are getting
more than 20!
I thank any idea you can give me.
Eddie
I'm new to this site and regarding the quality of the threads I'm confident
that I will get some help here. Here is the case:
We have a huge asp.net c# (101 bins and more than 4.000 aspx)(.net
framework 1.0, latest sp) internet site in W2K plataform. And since last
week, every time someone deploys new pages or assemblies the site goes
made. It recycles every 10 to 20 minutes until you go and reboot the
machine.
Our deployment time uses this procedure:
- stop WWW.
- execute iisreset.
- clean C:\WINNT\Microsoft.NET\Framework\v1.0.3705\Temporary ASP.NET Files
- make the deploy (xcopy the files).
- start WWW.
Last Friday I managed to understand what was going on, they have misplaced
the files and created copies of the directories in wrong places and I think
..net had a hard time serving this application. However yesterday it started
recycling again and for my total surprise nothing seems to be wrong with
the site.
Our application saves logs in the event viewer like that for each recycle:
Event Type: Warning
Event Source: portal.WEB
Event Category: (200)
Event ID: 111
Date: 12/4/2005
Time: 10:49:00
User: N/A
Computer: CAUDES2KATIX
Description:
<ACALog><LogCategory>AppAudit</LogCategory><Header>ClientApplication -
Application End</Header><EventID>111</EventID><Body><Message>Finalizando
aplica??o:
at App.MCA.Global.Application_End(Object, EventArgs)
at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object,
BindingFlags, Binder, Object[], CultureInfo, Boolean, Assembly, Boolean)
at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object,
BindingFlags, Binder, Object[], CultureInfo, Boolean)
at System.Reflection.RuntimeMethodInfo.Invoke(Object, BindingFlags,
Binder, Object[], CultureInfo)
at System.Web.HttpApplication.ProcessSpecialRequest(HttpContext,
MethodInfo, Int32, Object, EventArgs, HttpSessionState)
at System.Web.HttpApplicationFactory.FireApplicationOnEnd()
at System.Web.HttpApplicationFactory.Dispose()
at System.Web.HttpRuntime.Dispose()
at System.Web.HttpRuntime.ReleaseResourcesAndUnloadAppDomain(Object)
</Message><Src>Global.Application_End</Src><contextItems
/></Body><Severity>2</Severity><MachineName>CAUDES2KATIX</MachineName><DateTime>12/4/2005
10:49:00</DateTime></ACALog>
Microsoft say that when you get ReleaseResourcesAndUnloadAppDomain() is
because you have changed something on the application's directory (bins,
web.config, machine.config, etc) and this is asp.net way to week itself up-
to-date.
We were supposed to get just one recycle per deployment and we are getting
more than 20!
I thank any idea you can give me.
Eddie