|
|
|
date: Thu, 28 Aug 2008 13:38:11 +0200,
group: microsoft.public.inetserver.iis
back
Re: Recycling the pool ?
You dont need to create another AppPoll, except that other websites in the
AppPool use a differente version of framework.
If you have other web sites could be good to create an application pool for
the webservice ... this will isolate your webservice from problems that
could cause other web sites, like:
- Memory use that can cause OutOfMemoryExceptions
- Threads use that could leave the AppPool without threads to response
your web services request
- Hanging AppPoll
- Making reciclying of the AppPool
But, this cause an overhead of administration and memory use ... you must
evaluate your case.
About the recycling, this could be usefull to release resources ... I think
that setting the recycle after one hour of inactivity is right.
If your servie is stopped ... first, try to find what stop your site ...
after that, you can start the web site from administration console.
If the IIS is down ... run iisreset /start
Saludos!
"Oriane" <oriane@noemail.noemail> wrote in message
news:O$UbiKQCJHA.2056@TK2MSFTNGP05.phx.gbl...
> Hello,
>
> I will soon installed a small Ajax Asp.Net "single page" site on a client
> site. This page is simply polling a Asp.Net Web service, which fetchs and
> returns parameters (temperature, air conditioning status...) to be
> displayed on the page. This is implemented with an Ajax Timer control
> server.
>
> Now this is my first "industrial" web site, and I'm concerned about its
> robustness.
> Do I need to create a specific pool on IIS 6 for the web service and the
> site ?
> I'm aware than it is possible to "recycle" a pool. Do I need this ?
> If the site/service is down, how can I automaticllay try to restart it ?
>
> Best regards
>
date: Thu, 28 Aug 2008 13:55:43 -0300
author: Pablo A. Allois
RE: Recycling the pool ?
Hi Oriane,
It's always good to put different web applications into different
application pools. This will make them run into their own worker
processes(w3wp.exe) which means resources allocation is isolated(CPU,
memory, I/O, etc) and will not affect each other.
By default, IIS will shutdown an application pool's worker process instance
if it's idle for 20 mins(no requests come in). A new instance will be
started up at the time of next request is received. The effect is similar
to application pool recycling. So generally you don't need to manually do
any recycling jobs. If the site is a quite busy one, one thing you can
consider is enforce a pool recycling at a disengaged time(e.g midnight).
This can be set in application pool's property recycling tab.
About sites automatic restarting, in an application pool's health tab,
there is a rapid-fail protection setting. If this option is disabled, IIS
will always try to restart the pool instance when its worker process
encounters exception and terminated unexpectedly(sites in the pool get
down). The default setting is: if failures occur 5 times for this pool's
instances in 5 mins, IIS will automatically disable this application pool.
You can adjust the settings to achieve your goal.
Please update here if you have any further question.
Have a nice weekend.
Sincerely,
WenJun Zhang
Microsoft Online Community Support
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsoft.com.
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://support.microsoft.com/select/default.aspx?target=assistance&ln=en-us.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
date: Fri, 29 Aug 2008 08:16:52 GMT
author: (WenJun Zhang[msft])
|
|
