|
|
|
date: Tue, 29 Jul 2008 12:56:33 -0400,
group: microsoft.public.inetserver.iis
back
Re: Why is aspnet_wp.exe still alive after web site is stopped in IIS
Why do you need to do that? You don't need/want to recycle the process
hosting managed code. The reason you don't have that knob to turn is
because you shouldn't be turning that knob.
If you want to recycle to replace a managed assembly, simply copy it
over the original. ASP.Net is actually running a copy of the assembly
elsewhere and will detect this change and dynamically update.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
On Jul 29, 12:09 pm, "Lei Tang" wrote:
> David,
>
> Thank you so much!
>
> Is there any way to stop aspnet_wp.exe completely, for instance if I want to
> recycle the aspnet_wp.exe process once for a while?
>
> "David Wang" wrote in message
>
> news:01bb71d8-82fd-4aee-ba44-648a910f48f9@q5g2000prf.googlegroups.com...
> On Jul 29, 9:56 am, "Lei Tang" wrote:
>
> > I have IIS 5.1 on Windows XP. I noticed that the process aspnet_wp.exe was
> > still alive after I stopped the web site in IIS. Even more strange, every
> > time after I killed aspnet_wp.exe from Task Manager, a new aspnet_wp.exe
> > process was created immediately. Does anybody know why this was happening?
>
> What you observe is how the system works.
>
> Stopping a web site does not mean "kill/stop all associated
> processes". It means to stop taking incoming requests. Remember, it
> takes time to start up the new aspnet_wp.exe processes.
>
> If you kill aspnet_wp.exe, there is code monitoring for such behavior
> to start up a replacement aspnet_wp.exe. This is to minimize the
> amount of time an incoming request takes before being processed.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> //
date: Wed, 30 Jul 2008 03:56:36 -0700 (PDT)
author: David Wang
Re: Why is aspnet_wp.exe still alive after web site is stopped in IIS
My aspnet_wp.exe consumes fair amount of memories and I would like to shut
it down completely when I am not working with it. Another reason off the
top of my head would be debugging, for instance sometimes I need to
repeatedly debug the code in the function Application_Start
(Global.asax.cs) - I know there are alternative ways to do this (i.e. using
ASP.NET developement server) but I still think it would be convenient if we
can directly recyle the process aspnet_wp.exe.
"David Wang" wrote in message
news:7f270a70-5de9-43e7-a11c-434bf9a67e16@z11g2000prl.googlegroups.com...
Why do you need to do that? You don't need/want to recycle the process
hosting managed code. The reason you don't have that knob to turn is
because you shouldn't be turning that knob.
If you want to recycle to replace a managed assembly, simply copy it
over the original. ASP.Net is actually running a copy of the assembly
elsewhere and will detect this change and dynamically update.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
On Jul 29, 12:09 pm, "Lei Tang" wrote:
> David,
>
> Thank you so much!
>
> Is there any way to stop aspnet_wp.exe completely, for instance if I want
> to
> recycle the aspnet_wp.exe process once for a while?
>
> "David Wang" wrote in message
>
> news:01bb71d8-82fd-4aee-ba44-648a910f48f9@q5g2000prf.googlegroups.com...
> On Jul 29, 9:56 am, "Lei Tang" wrote:
>
> > I have IIS 5.1 on Windows XP. I noticed that the process aspnet_wp.exe
> > was
> > still alive after I stopped the web site in IIS. Even more strange,
> > every
> > time after I killed aspnet_wp.exe from Task Manager, a new aspnet_wp.exe
> > process was created immediately. Does anybody know why this was
> > happening?
>
> What you observe is how the system works.
>
> Stopping a web site does not mean "kill/stop all associated
> processes". It means to stop taking incoming requests. Remember, it
> takes time to start up the new aspnet_wp.exe processes.
>
> If you kill aspnet_wp.exe, there is code monitoring for such behavior
> to start up a replacement aspnet_wp.exe. This is to minimize the
> amount of time an incoming request takes before being processed.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> //
date: Wed, 30 Jul 2008 11:55:44 -0400
author: Lei Tang
Re: Why is aspnet_wp.exe still alive after web site is stopped in IIS
Your usage pattern is development-oriented. Use the ASP.Net
development server for that level of control on XP.
IIS 5.1 on Windows XP does not have a process model to support on-
demand recycling of ASP.Net. IIS 6 Does. Also, ASP.Net does not give
you knobs for on-demand recycling (it has automatic recycling
parameters) -- so what you want to do will never be convenient on XP.
You can shutdown inetinfo.exe, which contains the code that spins up
the aspnet_wp.exe, but that shuts down the entire IIS server.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
On Jul 30, 8:55 am, "Lei Tang" wrote:
> My aspnet_wp.exe consumes fair amount of memories and I would like to shut
> it down completely when I am not working with it. Another reason off the
> top of my head would be debugging, for instance sometimes I need to
> repeatedly debug the code in the function Application_Start
> (Global.asax.cs) - I know there are alternative ways to do this (i.e. using
> ASP.NET developement server) but I still think it would be convenient if we
> can directly recyle the process aspnet_wp.exe.
>
> "David Wang" wrote in message
>
> news:7f270a70-5de9-43e7-a11c-434bf9a67e16@z11g2000prl.googlegroups.com...
> Why do you need to do that? You don't need/want to recycle the process
> hosting managed code. The reason you don't have that knob to turn is
> because you shouldn't be turning that knob.
>
> If you want to recycle to replace a managed assembly, simply copy it
> over the original. ASP.Net is actually running a copy of the assembly
> elsewhere and will detect this change and dynamically update.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> //
>
> On Jul 29, 12:09 pm, "Lei Tang" wrote:
>
>
>
> > David,
>
> > Thank you so much!
>
> > Is there any way to stop aspnet_wp.exe completely, for instance if I want
> > to
> > recycle the aspnet_wp.exe process once for a while?
>
> > "David Wang" wrote in message
>
> >news:01bb71d8-82fd-4aee-ba44-648a910f48f9@q5g2000prf.googlegroups.com...
> > On Jul 29, 9:56 am, "Lei Tang" wrote:
>
> > > I have IIS 5.1 on Windows XP. I noticed that the process aspnet_wp.exe
> > > was
> > > still alive after I stopped the web site in IIS. Even more strange,
> > > every
> > > time after I killed aspnet_wp.exe from Task Manager, a new aspnet_wp.exe
> > > process was created immediately. Does anybody know why this was
> > > happening?
>
> > What you observe is how the system works.
>
> > Stopping a web site does not mean "kill/stop all associated
> > processes". It means to stop taking incoming requests. Remember, it
> > takes time to start up the new aspnet_wp.exe processes.
>
> > If you kill aspnet_wp.exe, there is code monitoring for such behavior
> > to start up a replacement aspnet_wp.exe. This is to minimize the
> > amount of time an incoming request takes before being processed.
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > //- Hide quoted text -
>
> - Show quoted text -
date: Wed, 30 Jul 2008 10:55:10 -0700 (PDT)
author: David Wang
|
|
