Re: Timeout period not seeming to work correctly

You might want to take a look at the setting
for recycling the ASP.NET worker process.

When you use InProc session state management,
and the worker process recycles, your application
restarts, causing the loss of all your session variables,
if you're using InProc state management.

Open the IIS MMC, and scroll down to Application Pools.
Check the recycling settings for short recycle periods and adjust if necessary.

You might also want to consider using State Server or SQL Server
State management, instead of InProc, since they persist Session
settings when the ASP.NET worker processes are recycled.



Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
======================

"tshad" <tscheiderich@xxxxxxxxxxxxxxx> wrote in message
news:OVWaDlIbFHA.1660@xxxxxxxxxxxxxxxxxxxxxxx
>I am still having the problem even with the fixes below.
>
> The first part of my web.config is:
>
> <configuration>
> <system.web>
> <customErrors mode="Off"/>
> <sessionState
> mode="InProc"
> cookieless="false"
> timeout="400"
> />
> <authentication mode="Forms">
> <forms name="staffing"
> loginUrl="/applicant/EELogin.aspx"
> timeout="400"
> protection="All"
> path="/" />
> </authentication>
>
> I have both forms and sessionState to timeout at 400 minutes.
>
> The problem is that after about 20-30 minutes of just going back and forth using the
> same page (as I am testing the page), all of a sudden all my session variables are gone.
> They shouldn't be gone for hours.
>
> What else am I missing?
>
> I need to figure this out as we are going to be showing this to some people and I don't
> want the page timing in 20 minutes.
>
> Thanks,
>
> Tom
>
> "tshad" <tscheiderich@xxxxxxxxxxxxxxx> wrote in message
> news:eI9ZJ7FbFHA.1088@xxxxxxxxxxxxxxxxxxxxxxx
>> "Ronald Lemmen" <muis007@xxxxxxxxxxx> wrote in message
>> news:1118243440.300634.81600@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>> You are probably getting the error because the web.config is
>>> casesensitive. That means that you should not enter sessionstate, but
>>> use sessionState instead.
>>>
>>
>> That was it.
>>
>> I also had to use "InProc" instead of "inproc".
>>
>> I never could figure out what the problem was and was going to come back to it later.
>>
>> Thanks,
>>
>> Tom
>>
>>> Hope this helps,
>>>
>>> Ronald Lemmen
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: Recycled Application Pool
    ... There's different ways to manage IIS 5 and IIS 6. ... recycling settings, to see if anything rings a bell. ... If you need to persist your session values, ... IIS's State Server or with SQL Server. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: IIS 6.0 Session expired with the following simple ASP lines?!?
    ... the session expires before the defined timeout if ... the application pool is recycling. ... I use this code to determine if the application is recycling: ... oh, btw, session and cookies are not the perfect way to work, write your own ...
    (microsoft.public.inetserver.iis)
  • Re: Session Timeout Problem
    ... "recycling threshold settings" in IIS. ... My original question at the ... Have you attempted to set a different recycling threshold in the IIS ... session variables due to Application/App Pool recycling. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Timeout period not seeming to work correctly
    ... > for recycling the ASP.NET worker process. ... > restarts, causing the loss of all your session variables, ... > if you're using InProc state management. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Live multi-user debugging? Help!
    ... Memory recycling: well, if it comes to that, either add more RAM or find the ... session state (if so, look out for the session state timeout for the web ... have another one going so that people can still use the web site. ...
    (microsoft.public.dotnet.languages.vb)