 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / IIS / IIS General Topics / July 2008Why is aspnet_wp.exe still alive after web site is stopped in IIS
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? > 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. //David http://w3-4u.blogspot.com http://blogs.msdn.com/David.Wang // 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? On Jul 29, 9:56 am, "Lei Tang" <lt...@bdmetrics.com> 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. //David http://w3-4u.blogspot.com http://blogs.msdn.com/David.Wang // 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 // > David, > [quoted text clipped - 22 lines] > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang > // 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. 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" <lt...@bdmetrics.com> wrote: > David, > [quoted text clipped - 28 lines] > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang > // 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 // > 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 [quoted text clipped - 51 lines] > > - Show quoted text - |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.