Re: Timeout period not seeming to work correctly
- From: "tshad" <tscheiderich@xxxxxxxxxxxxxxx>
- Date: Thu, 9 Jun 2005 08:44:07 -0700
"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.
>
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
>>>>
>>>
>>>
>>
>>
>
>
.
- Follow-Ups:
- Re: Timeout period not seeming to work correctly
- From: tshad
- Re: Timeout period not seeming to work correctly
- References:
- Re: Timeout period not seeming to work correctly
- From: Ronald Lemmen
- Re: Timeout period not seeming to work correctly
- From: tshad
- Re: Timeout period not seeming to work correctly
- From: tshad
- Re: Timeout period not seeming to work correctly
- From: Juan T. Llibre
- Re: Timeout period not seeming to work correctly
- Prev by Date: ImageMap + SQL Server + ASP.NET question...
- Next by Date: Issue with pdf load using response.binarywrite
- Previous by thread: Re: Timeout period not seeming to work correctly
- Next by thread: Re: Timeout period not seeming to work correctly
- Index(es):
Relevant Pages
|