Application pool idle timeout in IIS 5.1

In IIS 6.0, I can set the Application pool idle timeout in the Application
Pool properties window ("Shutdown worker processes after being idle for" n
minutes, the default being 20 minutes). Is there a way to do something
similar in IIS 5.1?

--
Thank you,

Alain Quesnel
alainsansspam [at] logiquel.com

www.logiquel.com
Alain Quesnel [ Mo, 14 Januar 2008 18:52 ] [ ID #1907433 ]

Re: Application pool idle timeout in IIS 5.1

On Jan 14, 9:52=A0am, "Alain Quesnel" <alainsanss... [at] logiquel.com>
wrote:
> In IIS 6.0, I can set the Application pool idle timeout in the Application=

> Pool properties window ("Shutdown worker processes after being idle for" n=

> minutes, the default being 20 minutes). Is there a way to do something
> similar in IIS 5.1?
>
> --
> Thank you,
>
> Alain Quesnel
> alainsanss... [at] logiquel.com
>
> www.logiquel.com


No. Application Pools is a feature introduced with IIS6 and does not
exist in IIS5.1.

Closest thing on XP Pro is COM+ Application Settings, but it does not
work as you think.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
David Wang [ Di, 15 Januar 2008 01:29 ] [ ID #1908422 ]

Re: Application pool idle timeout in IIS 5.1

Is there a way to prevent ASP/IIS 5 from "falling asleep" if there are no
requests for a while? I use Miscrosoft Reporting Services. When I open the
first report, it takes 30 to 60 seconds to come up. After that, it's much
faster (a few seconds at the most). I'm trying to find a way to keep IIS and
ASP ready to fire, so to speak.


Thank you,

Alain Quesnel
alainsansspam [at] logiquel.com

www.logiquel.com


"David Wang" <w3.4you [at] gmail.com> wrote in message
news:6515564b-dde7-4b4b-a676-11af77469639 [at] e4g2000hsg.googleg roups.com...
On Jan 14, 9:52 am, "Alain Quesnel" <alainsanss... [at] logiquel.com>
wrote:
> In IIS 6.0, I can set the Application pool idle timeout in the Application
> Pool properties window ("Shutdown worker processes after being idle for" n
> minutes, the default being 20 minutes). Is there a way to do something
> similar in IIS 5.1?
>
> --
> Thank you,
>
> Alain Quesnel
> alainsanss... [at] logiquel.com
>
> www.logiquel.com


No. Application Pools is a feature introduced with IIS6 and does not
exist in IIS5.1.

Closest thing on XP Pro is COM+ Application Settings, but it does not
work as you think.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
Alain Quesnel [ Di, 15 Januar 2008 03:19 ] [ ID #1908426 ]

Re: Application pool idle timeout in IIS 5.1

Are you refering to ASP or ASP.Net -- because I don't think ASP clears
its cache like that.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Jan 14, 6:19=A0pm, "Alain Quesnel" <alainsanss... [at] logiquel.com>
wrote:
> Is there a way to prevent ASP/IIS 5 from "falling asleep" if there are no
> requests for a while? I use Miscrosoft Reporting Services. When I open the=

> first report, it takes 30 to 60 seconds to come up. After that, it's much
> faster (a few seconds at the most). I'm trying to find a way to keep IIS a=
nd
> ASP ready to fire, so to speak.
>
> Thank you,
>
> Alain Quesnel
> alainsanss... [at] logiquel.com
>
> www.logiquel.com
>
> "David Wang" <w3.4... [at] gmail.com> wrote in message
>
> news:6515564b-dde7-4b4b-a676-11af77469639 [at] e4g2000hsg.googleg roups.com...
> On Jan 14, 9:52 am, "Alain Quesnel" <alainsanss... [at] logiquel.com>
> wrote:
>
> > In IIS 6.0, I can set the Application pool idle timeout in the Applicati=
on
> > Pool properties window ("Shutdown worker processes after being idle for"=
n
> > minutes, the default being 20 minutes). Is there a way to do something
> > similar in IIS 5.1?
>
> > --
> > Thank you,
>
> > Alain Quesnel
> > alainsanss... [at] logiquel.com
>
> >www.logiquel.com
>
> No. Application Pools is a feature introduced with IIS6 and does not
> exist in IIS5.1.
>
> Closest thing on XP Pro is COM+ Application Settings, but it does not
> work as you think.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //
David Wang [ Di, 15 Januar 2008 12:30 ] [ ID #1908434 ]

Re: Application pool idle timeout in IIS 5.1

I use Reporting Services 2005 SP2 (which uses ASP.NET 2.0) on XP Pro SP2
(IIS 5.1).

--
Thank you,

Alain Quesnel
alainsansspam [at] logiquel.com

www.logiquel.com


"David Wang" <w3.4you [at] gmail.com> wrote in message
news:960bf745-7e3b-48fa-a2a6-4a143792fd9f [at] e32g2000prn.google groups.com...
Are you refering to ASP or ASP.Net -- because I don't think ASP clears
its cache like that.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Jan 14, 6:19 pm, "Alain Quesnel" <alainsanss... [at] logiquel.com>
wrote:
> Is there a way to prevent ASP/IIS 5 from "falling asleep" if there are no
> requests for a while? I use Miscrosoft Reporting Services. When I open the
> first report, it takes 30 to 60 seconds to come up. After that, it's much
> faster (a few seconds at the most). I'm trying to find a way to keep IIS
> and
> ASP ready to fire, so to speak.
>
> Thank you,
>
> Alain Quesnel
> alainsanss... [at] logiquel.com
>
> www.logiquel.com
>
> "David Wang" <w3.4... [at] gmail.com> wrote in message
>
> news:6515564b-dde7-4b4b-a676-11af77469639 [at] e4g2000hsg.googleg roups.com...
> On Jan 14, 9:52 am, "Alain Quesnel" <alainsanss... [at] logiquel.com>
> wrote:
>
> > In IIS 6.0, I can set the Application pool idle timeout in the
> > Application
> > Pool properties window ("Shutdown worker processes after being idle for"
> > n
> > minutes, the default being 20 minutes). Is there a way to do something
> > similar in IIS 5.1?
>
> > --
> > Thank you,
>
> > Alain Quesnel
> > alainsanss... [at] logiquel.com
>
> >www.logiquel.com
>
> No. Application Pools is a feature introduced with IIS6 and does not
> exist in IIS5.1.
>
> Closest thing on XP Pro is COM+ Application Settings, but it does not
> work as you think.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //
Alain Quesnel [ Di, 15 Januar 2008 14:46 ] [ ID #1908440 ]

Re: Application pool idle timeout in IIS 5.1

Thanks for clarifying.

BTW, ASP and ASP.Net are totally different. The only thing they have
in common are the letters "A", "S", and "P".

I was not expecting 30-60 seconds startup from ASP -- that sounds much
more consistent with the well-known CLR Startup time for ASP.Net.

On IIS 5/5.1, and IIS6 in IIS5 Compatibility Mode, ASP.Net uses its
own process model (similar but not exactly the same as IIS6
Application Pools), not COM+. Please search for <processModel> on the
Web for the idleTimeout setting and change it in the machine.config of
the version of the .Net framework versioned for your ASP.Net version.

machine.config for ASP.Net 2.0 should be in:
%windir%\Microsoft.Net\Framework\v2.0.50727\config\machine.c onfig

The reason that IIS "falls asleep" is because your website is not
getting the traffic to warrant having the application in memory, so it
shuts down the application to reclaim the memory for something else on
the server. Of course, if you have a dedicated server for the
application (which you've never told IIS about), you can certainly
tell IIS to stop prematurely shutting down the application to reclaim
memory because it's not going to be used for anything else.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//





On Jan 15, 5:46=A0am, "Alain Quesnel" <alainsanss... [at] logiquel.com>
wrote:
> I use Reporting Services 2005 SP2 (which uses ASP.NET 2.0) on XP Pro SP2
> (IIS 5.1).
>
> --
> Thank you,
>
> Alain Quesnel
> alainsanss... [at] logiquel.com
>
> www.logiquel.com
>
> "David Wang" <w3.4... [at] gmail.com> wrote in message
>
> news:960bf745-7e3b-48fa-a2a6-4a143792fd9f [at] e32g2000prn.google groups.com...
> Are you refering to ASP or ASP.Net -- because I don't think ASP clears
> its cache like that.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //
>
> On Jan 14, 6:19 pm, "Alain Quesnel" <alainsanss... [at] logiquel.com>
> wrote:
>
>
>
> > Is there a way to prevent ASP/IIS 5 from "falling asleep" if there are n=
o
> > requests for a while? I use Miscrosoft Reporting Services. When I open t=
he
> > first report, it takes 30 to 60 seconds to come up. After that, it's muc=
h
> > faster (a few seconds at the most). I'm trying to find a way to keep IIS=

> > and
> > ASP ready to fire, so to speak.
>
> > Thank you,
>
> > Alain Quesnel
> > alainsanss... [at] logiquel.com
>
> >www.logiquel.com
>
> > "David Wang" <w3.4... [at] gmail.com> wrote in message
>
> >news:6515564b-dde7-4b4b-a676-11af77469639 [at] e4g2000hsg.google groups.com...
> > On Jan 14, 9:52 am, "Alain Quesnel" <alainsanss... [at] logiquel.com>
> > wrote:
>
> > > In IIS 6.0, I can set the Application pool idle timeout in the
> > > Application
> > > Pool properties window ("Shutdown worker processes after being idle fo=
r"
> > > n
> > > minutes, the default being 20 minutes). Is there a way to do something=

> > > similar in IIS 5.1?
>
> > > --
> > > Thank you,
>
> > > Alain Quesnel
> > > alainsanss... [at] logiquel.com
>
> > >www.logiquel.com
>
> > No. Application Pools is a feature introduced with IIS6 and does not
> > exist in IIS5.1.
>
> > Closest thing on XP Pro is COM+ Application Settings, but it does not
> > work as you think.
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > //- Hide quoted text -
>
> - Show quoted text -
David Wang [ Mi, 16 Januar 2008 09:21 ] [ ID #1909613 ]

Re: Application pool idle timeout in IIS 5.1

I googled <processModel> and I found this page:
http://msdn2.microsoft.com/en-us/library/7w2sway1(VS.71).asp x

On it, the "idletimeout" attribute is described as follows:

"Specifies the period of inactivity, in hr:min:sec string format, after
which ASP.NET automatically ends the worker process. The default is
Infinite."

I'm not sure I understand. Does that mean the default setting will keep a
worker process going for an infinite amount of time, regardless of its
repeated usage i.e. hits on the website (or lack thereof)? I looked at my
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine .config file.
The only attribute I have under <processmodel> is autoConfig="true", which
is not described on the web page I mentioned above.

I added this attribute to the machine.config file.

idleTimeout="16:00:00"

I'll see if that works.

--
Thank you,

Alain Quesnel
alainsansspam [at] logiquel.com

www.logiquel.com


"David Wang" <w3.4you [at] gmail.com> wrote in message
news:debfe2a9-0e28-4cb0-8eeb-0b26dfd4f47a [at] i12g2000prf.google groups.com...
Thanks for clarifying.

BTW, ASP and ASP.Net are totally different. The only thing they have
in common are the letters "A", "S", and "P".

I was not expecting 30-60 seconds startup from ASP -- that sounds much
more consistent with the well-known CLR Startup time for ASP.Net.

On IIS 5/5.1, and IIS6 in IIS5 Compatibility Mode, ASP.Net uses its
own process model (similar but not exactly the same as IIS6
Application Pools), not COM+. Please search for <processModel> on the
Web for the idleTimeout setting and change it in the machine.config of
the version of the .Net framework versioned for your ASP.Net version.

machine.config for ASP.Net 2.0 should be in:
%windir%\Microsoft.Net\Framework\v2.0.50727\config\machine.c onfig

The reason that IIS "falls asleep" is because your website is not
getting the traffic to warrant having the application in memory, so it
shuts down the application to reclaim the memory for something else on
the server. Of course, if you have a dedicated server for the
application (which you've never told IIS about), you can certainly
tell IIS to stop prematurely shutting down the application to reclaim
memory because it's not going to be used for anything else.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//





On Jan 15, 5:46 am, "Alain Quesnel" <alainsanss... [at] logiquel.com>
wrote:
> I use Reporting Services 2005 SP2 (which uses ASP.NET 2.0) on XP Pro SP2
> (IIS 5.1).
>
> --
> Thank you,
>
> Alain Quesnel
> alainsanss... [at] logiquel.com
>
> www.logiquel.com
>
> "David Wang" <w3.4... [at] gmail.com> wrote in message
>
> news:960bf745-7e3b-48fa-a2a6-4a143792fd9f [at] e32g2000prn.google groups.com...
> Are you refering to ASP or ASP.Net -- because I don't think ASP clears
> its cache like that.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //
>
> On Jan 14, 6:19 pm, "Alain Quesnel" <alainsanss... [at] logiquel.com>
> wrote:
>
>
>
> > Is there a way to prevent ASP/IIS 5 from "falling asleep" if there are
> > no
> > requests for a while? I use Miscrosoft Reporting Services. When I open
> > the
> > first report, it takes 30 to 60 seconds to come up. After that, it's
> > much
> > faster (a few seconds at the most). I'm trying to find a way to keep IIS
> > and
> > ASP ready to fire, so to speak.
>
> > Thank you,
>
> > Alain Quesnel
> > alainsanss... [at] logiquel.com
>
> >www.logiquel.com
>
> > "David Wang" <w3.4... [at] gmail.com> wrote in message
>
> >news:6515564b-dde7-4b4b-a676-11af77469639 [at] e4g2000hsg.google groups.com...
> > On Jan 14, 9:52 am, "Alain Quesnel" <alainsanss... [at] logiquel.com>
> > wrote:
>
> > > In IIS 6.0, I can set the Application pool idle timeout in the
> > > Application
> > > Pool properties window ("Shutdown worker processes after being idle
> > > for"
> > > n
> > > minutes, the default being 20 minutes). Is there a way to do something
> > > similar in IIS 5.1?
>
> > > --
> > > Thank you,
>
> > > Alain Quesnel
> > > alainsanss... [at] logiquel.com
>
> > >www.logiquel.com
>
> > No. Application Pools is a feature introduced with IIS6 and does not
> > exist in IIS5.1.
>
> > Closest thing on XP Pro is COM+ Application Settings, but it does not
> > work as you think.
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > //- Hide quoted text -
>
> - Show quoted text -
Alain Quesnel [ Mi, 16 Januar 2008 19:55 ] [ ID #1909628 ]
Webserver » microsoft.public.inetserver.iis » Application pool idle timeout in IIS 5.1

Vorheriges Thema: apache web proxy and IIS6
Nächstes Thema: include virtual not working on IIS 7/Vista Ultimate