tag:blogger.com,1999:blog-8908362316203403946.post1751826247459418443..comments2010-02-15T07:15:17.227+05:30ma_khannoreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8908362316203403946.post-59197301834623039832010-02-15T07:15:17.227+05:302010-02-15T07:15:17.227+05:30to smalcat: the problem is not Recycling, as Recycling starts new WP and kills the old one. The problem is IdleTimeout which shuts down the process without starting the replacement. Just turn off IdleTimeout via Performance tab and it should be ok.<br /><br />Thanx for the article!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8908362316203403946.post-13313862780855299552009-07-22T15:43:36.214+05:302009-07-22T15:43:36.214+05:30I have a bit different question concerning the recycling. <br /><br />My webservice has a requirement to load 2GB of data into memory, which is afterwards used at every request. Everything works fine, except the first request hitting after the recycle, needs to wait additional time for data to load. <br /><br />My question: is there a way to automatically start the webservice in IIS6. Some kind of a warm up script? I dont want to program a client whose sole point would be to make a request after each recycle.smalcatnoreply@blogger.comtag:blogger.com,1999:blog-8908362316203403946.post-44565818439078316952008-12-13T22:52:00.000+05:302008-12-13T22:52:00.000+05:30Brillant Summary of IIS6\App PoolsPJBhttp://www.blogger.com/profile/17000240811325243678noreply@blogger.com