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@logiquel.com

www.logiquel.com

On Jan 14, 9:52*am, "Alain Quesnel" <alainsanss...@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...@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
//

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@logiquel.com

www.logiquel.com


"David Wang" <w3.4you@gmail.com> wrote in message
news:6515564b-dde7-4b4b-a676-11af77469639@e4g2000hsg.googlegroups.com...
On Jan 14, 9:52 am, "Alain Quesnel" <alainsanss...@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...@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
//

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...@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...@logiquel.com
>
> www.logiquel.com
>
> "David Wang" <w3.4...@gmail.com> wrote in message
>
> news:6515564b-dde7-4b4b-a676-11af77469639@e4g2000hsg.googlegroups.com...
> On Jan 14, 9:52 am, "Alain Quesnel" <alainsanss...@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...@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
> //

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

--
Thank you,

Alain Quesnel
alainsansspam@logiquel.com

www.logiquel.com


"David Wang" <w3.4you@gmail.com> wrote in message
news:960bf745-7e3b-48fa-a2a6-4a143792fd9f@e32g2000prn.googlegroups.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...@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...@logiquel.com
>
> www.logiquel.com
>
> "David Wang" <w3.4...@gmail.com> wrote in message
>
> news:6515564b-dde7-4b4b-a676-11af77469639@e4g2000hsg.googlegroups.com...
> On Jan 14, 9:52 am, "Alain Quesnel" <alainsanss...@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...@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
> //

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.config

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...@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...@logiquel.com
>
> www.logiquel.com
>
> "David Wang" <w3.4...@gmail.com> wrote in message
>
> news:960bf745-7e3b-48fa-a2a6-4a143792fd9f@e32g2000prn.googlegroups.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...@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...@logiquel.com
>
> >www.logiquel.com
>
> > "David Wang" <w3.4...@gmail.com> wrote in message
>
> >news:6515564b-dde7-4b4b-a676-11af77469639@e4g2000hsg.googlegroups.com...
> > On Jan 14, 9:52 am, "Alain Quesnel" <alainsanss...@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...@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 -

I googled <processModel> and I found this page:
http://msdn2.microsoft.com/en-us/lib...y1(VS.71).aspx

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\CONF IG\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@logiquel.com

www.logiquel.com


"David Wang" <w3.4you@gmail.com> wrote in message
news:debfe2a9-0e28-4cb0-8eeb-0b26dfd4f47a@i12g2000prf.googlegroups.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.config

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...@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...@logiquel.com
>
> www.logiquel.com
>
> "David Wang" <w3.4...@gmail.com> wrote in message
>
> news:960bf745-7e3b-48fa-a2a6-4a143792fd9f@e32g2000prn.googlegroups.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...@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...@logiquel.com
>
> >www.logiquel.com
>
> > "David Wang" <w3.4...@gmail.com> wrote in message
>
> >news:6515564b-dde7-4b4b-a676-11af77469639@e4g2000hsg.googlegroups.com...
> > On Jan 14, 9:52 am, "Alain Quesnel" <alainsanss...@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...@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 -

Salut Espen,

The idleTimeout="23:59:00" in the machine.config file works fine in IIS 5.1
(on Windows XP Pro). I also scheduled a dummy report that runs every day at
4AM. Now, everytime I hit my Reporting Services webpage, I have no more
delays whatsoever.

If you're using IIS 6 (Windows 2003 Server), then you need to change the 20
minute value in the Application Pool properties window (see my first post in
this thread).


Alain Quesnel
alainsansspam@logiquel.com

www.logiquel.com

------------------------
Salut Alain,

I came across your question about keeping IIS 5 awake and "ready to fire":

Application pool idle timeout in IIS 5.1


I'm struggling with the same problem myself, but I see that you're over a
month ahead of me. May I be so bold as to ask if you have found a solution
yet. And if you care to share it.?? J

Did adding idleTimeout="16:00:00" to the machine.config help?

(Btw, in IIS 6 it seems "infinite" is a valid value.)


Thanks for your time,

Espen Sandall

(located in Norway)


mvh Espen

---

Please consider the environment before printing this e-mail