no, it's set to 40. Everythingis set to 40.
In Windows Server 2003, you can set the recycling threshhold
for the Application Pool in which an application runs.
In the IIS Manager, scroll down the left hand panel to "Application Pools",
and select the Application Pool in which your app runs.
Right-click the App Pool and select "Properties" from the context menu.
You'll see several options for setting the time/memory limit/number of requests
at which the application pool will be recycled.
Just make sure your time setting isn't set too low.
Leave the rest untouched until you are familiar with the settings.
You don't say whether you tried using State Server.
!> Also, have you tried to use State Server, instead of InProc state management?
!> State Server state management, as does SQL Server, gets around
!> the loss of session variables due to Application/App Pool recycling.
Just configure it in web.config :
...and in the "Services" applet of the W2K3 Server, start the State Server service.
That usually works to prevent Session variable losses.
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espaol : http://asp.net.do/foros/
@newsgroups.nospam> wrote in message
That was it. The other settings had already extended my Session.timeout but
then we were getting null session variables after 20 minutes. I didn't try
State Server because we just don't need it now for this low-arrival rate
Thank you very much for your help on this issue.
"Juan T. Llibre" <email@example.com> wrote in message