Re: Timeout period not seeming to work correctly


"tshad" <tscheiderich@xxxxxxxxxxxxxxx> wrote in message
news:uDE2ToQbFHA.3132@xxxxxxxxxxxxxxxxxxxxxxx
> "Juan T. Llibre" <nomailreplies@xxxxxxxxxxx> wrote in message
> news:%23DXD26IbFHA.3192@xxxxxxxxxxxxxxxxxxxxxxx
>> 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.
>
> I assume you are talking about the Idle timeout (as that was set for 20
> minutes).
>
> What is the drawback of having it for an hour? Does it slow things down
> or leave the session variables around for longer than 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.
>>
When the worker process recycles, you say you lose your Session variables,
do you also lose your ASP.NET_SessionId ? I found that if reset the web
server, I would lose my session variables, but not my ASP.NET_SessionId.

Also, does the Session_End event fire when the worker process recycles?

I know it does when you abandon it.

Thanks,

Tom

>
> I need to check out the pluses and minuses of these to decide which is
> best for us.
>
> I assume that InProc is default?
>
> Thanks,
>
> Tom
>
>>
>>
>> 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: Session State stateserver or Sql Server
    ... > the session variables. ... The *ASP.NET worker process* gets recycled. ... The whole purpose of using State Server is to store the session variables ... > If the worker process recycles at a different time then the session timeouts - what is ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: ISS 6.0 and tilde
    ... Unfortunately I can't test this just now as I have to run the server in IIS ... sessions persist in a classic ASP application without relying on session ... > What you are probably seeing, though, is that the worker process itself ... > not have access to check the file system for that file. ...
    (microsoft.public.inetserver.iis)
  • Re: [Full-disclosure] [WEB SECURITY] Preventing Cross-site Request Forgeries
    ... creating another layer of state management on top of the HTTP ... addition to the usual session state. ... solutions for workflow and pageflow. ... Additional levels of state management like these allow developers to ...
    (Full-Disclosure)
  • Re: session variables, Timeout and Recycling
    ... I would like to understand better the 'Shutdown worker process after being ... What does idle mean? ... Application and Session. ... as recycling the worker process) causes all of these items to get dumped - ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Worker process and Session state
    ... can host multiple domain. ... so a session id will be shared across a web garden or farm, ... If we create a web farm architecture, will each worker process be in it's ...
    (microsoft.public.dotnet.framework.aspnet)