Re: Recycled Application Pool
- From: "Juan T. Llibre" <nomailreplies@xxxxxxxxxxx>
- Date: Fri, 8 Apr 2005 07:52:08 -0400
I wish you'd identified your OS/IIS version.
There's different ways to manage IIS 5 and IIS 6.
For starters, you can look into the Application Pool's
recycling settings, to see if anything rings a bell.
Open the IIS MMC; scroll down to Application Pools;
select the Application Pool which is giving you trouble
if you have more than one AppPool, or the DefaultAppPool.
Then, right click the AppPool,
and select "Properties" from the context menu.
In the "Recycling", "Performance" and "Health" tabs,
you'll see various settings which you can change in order
to help IIS manage better your application's requests.
If you're using IIS 6.0, this cached article
( it's lost now in a maze of rewrites at TechNet and MSDN )
http://64.233.187.104/search?q=cache:mWYQ229VGOUJ:www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/ca_recycwrkrprocess.asp%3FFRAME%3DTrue+application+pool+recycles+IIS+solution&hl=en
will be quite helpful in order to understand the different options.
If you have enough resources ( RAM, mostly ),
you can increase the threshholds for the recycle to occur.
That really shouldn't be a problem, though.
IIS keeps honoring any "old" requests to a worker
process which has been scheduled for recycling.
Are you getting any recycling events in your Event log ?
This KB will help you understand what those messages mean :
http://support.microsoft.com/default.aspx?scid=kb;en-us;332088
Please examine the ""Explanation of flags " and the "Event log entries"
listings to get a grip on what they mean.
Don't use the adsutil.vbs script unless you have to.
Most problems can be solved using the IIS MMC interface.
Something you should *really* consider is
how you are handling your session data.
*That* could be the critical operation you need to modify.
If you need to persist your session values, you *cannot* run
Session State "InProc" ( in the same process as ASP.NET )
because, obviously, when the worker process recycles,
the session values will be lost.
You must run your session state either with
IIS's State Server or with SQL Server.
Session values persist through worker process recycles if you use them.
This a lot of info but, hey, you asked for it. :-)
Post back any additional questions you have.
best,
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
======================
"Lars Netzel" <uihsdf@xxxxxx> wrote in message
news:%23HB%236aAPFHA.3988@xxxxxxxxxxxxxxxxxxxxxxx
> Hi
>
> We have an ASP.NET application running on a Live server and we have had
> some problems with the Application pool beeing recycled due to heavy load
> on the server. The load is really not that bad and this should nto occur.
> The application is using a lot of Session varaibles but I have no idea if
> this is a problem. I need the session variabled to make passing varibles
> between pages more secure. We also have many Datasets in the session.
>
> What things should I start to look at to get rid of this problem?
>
> best regards
> /Lars
.
- References:
- Recycled Application Pool
- From: Lars Netzel
- Recycled Application Pool
- Prev by Date: RTf to Html with C#
- Next by Date: RegExp between tags
- Previous by thread: Re: Recycled Application Pool
- Next by thread: Web Application with Crystal Report
- Index(es):
Relevant Pages
|
