recycling the ASPNet_WP.EXE + application-state Objects get lost.

[Grinninger]

Hello,
I am using ASP.NET, C# under W2K.
I try to keep some important information in application- and
session-state Objects.
With the recycling of the ASPNet_WP.EXE my application- and
session-state Objects get lost.

Therfore I have some questions:
-) Is it usual that the ASPNet_WP.EXE becomes recycled twice a day?
-) What is the expected recyclingperiod for the ASPNet_WP.EXE ?
-) How to react on this situation?
-) What is the regular way to store Application Objects?



Hope to hear from you soon on this regard

Regards ,

Jörg Grinninger

 

[Karl Seguin]

Check out your machine.conf's processModel for information on recycling,
you'll see things like timeout, idleTimeout, memoryLimit and a few other
thigns which all affect process recycling.

I don't see how you are losing application objects..if the process recycles
the application_start event fires and all your application variables get
reloaded...no?!?!

As for your session-state stuff, it will get lost during recycles...your
only alternative is to store sessions out of process, such as in SQL Server
or Session State Manager...

Karl

 

[Grinninger]

Hi Karl,
I want to save a userinput for all sessions in an application-state
Object (without saving it to the disk).
So I can't reload this input automaticalls by application_start.

If there is no other way, I will have to try the Session State Manager
(even if this is pain).

thanks a lot

Jörg

 

[Karl Seguin]

Why is it a pain? You start a service and change your webconfig? There's a
good chance you were using the application object incorectly to begin
with...it isn't meant to store user-specific information...it's an
APPLICATION object....sessions are what you want..and if recycling is a
problem, state management offers a pretty simple solution.

Karl