Hello,
i'm struggling with a somehow badly understood session scenario.
I provide acces to my pages based on form authentication using
Session cookies.
Som of my pages are supposed to be running continuously and refreshing once
an hour.
I there set timeout= 61 in <sessionState section and on my page it says
<meta http-equiv="refresh" content="3600"> .
I also set timeout=120 in the <forms section of web.config to make sure
the cookie does not expire before the session has been renewed.
But anyway i'm getting the temeout every 3600 seconds.
Can someone explain this?
Many thanks in advance.
JB
17  5188 
Actually, it makes a lot of sense that, if you have
timeout= 61 in <sessionState , that the sessions
would expire in approximately 3600 seconds.
Remember that the timeout value is expressed in minutes.
If you need a higher expiration time for your sessions,
set timeout= in <sessionState to 120, if that's what you need.
If you do, the sessions will expire in 7200 seconds.
Take note that the larger the session expiration time,
the more memory consumption and that, at some point,
you might wind up with a recycled application due to
lack of sufficient RAM, and all your sessions will expire anyway.
You will have to experiment and look for a trade-off between
configured session expiration time and application recycling time.
Juan T. Llibre
ASP.NET MVP http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:uT******** ******@TK2MSFTN GP09.phx.gbl...
Hello,
i'm struggling with a somehow badly understood session scenario.
I provide acces to my pages based on form authentication using
Session cookies.
Som of my pages are supposed to be running continuously and refreshing
once an hour.
I there set timeout= 61 in <sessionState section and on my page it
says
<meta http-equiv="refresh" content="3600"> .
I also set timeout=120 in the <forms section of web.config to make sure
the cookie does not expire before the session has been renewed.
But anyway i'm getting the temeout every 3600 seconds.
Can someone explain this?
Many thanks in advance.
JB
But then how do i avoid my session to timeout still keeping the refresh
time to 1 hour (3600 seconds)?
"Juan T. Llibre" <no***********@ nowhere.com> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. .. Actually, it makes a lot of sense that, if you have
timeout= 61 in <sessionState , that the sessions
would expire in approximately 3600 seconds.
Remember that the timeout value is expressed in minutes.
If you need a higher expiration time for your sessions,
set timeout= in <sessionState to 120, if that's what you need.
If you do, the sessions will expire in 7200 seconds.
Take note that the larger the session expiration time,
the more memory consumption and that, at some point,
you might wind up with a recycled application due to
lack of sufficient RAM, and all your sessions will expire anyway.
You will have to experiment and look for a trade-off between
configured session expiration time and application recycling time.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:uT******** ******@TK2MSFTN GP09.phx.gbl...
Hello,
i'm struggling with a somehow badly understood session scenario.
I provide acces to my pages based on form authentication using
Session cookies.
Som of my pages are supposed to be running continuously and refreshing
once an hour.
I there set timeout= 61 in <sessionState section and on my page it
says
<meta http-equiv="refresh" content="3600"> .
I also set timeout=120 in the <forms section of web.config to make sure
the cookie does not expire before the session has been renewed.
But anyway i'm getting the temeout every 3600 seconds.
Can someone explain this?
Many thanks in advance.
JB
The refresh time is immaterial.
If you have your session timeout set to 20 minutes,
and have a meta refresh, in all your pages, set to 19 minutes,
you could have your sessions continually refreshed, without the
need to accumulate RAM resources over 120 minutes.
As long as a user has a page at your site open, the sessions
would be automatically extended for another 20 minutes.
If they close all pages at your site, i.e., if they go away
permanently, then the sessions would expire 20 minutes
after the last page open was refreshed.
There's really no need to have large session timeout values.
Juan T. Llibre
ASP.NET MVP http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:e%******** ********@TK2MSF TNGP15.phx.gbl. .. But then how do i avoid my session to timeout still keeping the refresh
time to 1 hour (3600 seconds)?
"Juan T. Llibre" <no***********@ nowhere.com> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. .. Actually, it makes a lot of sense that, if you have
timeout= 61 in <sessionState , that the sessions
would expire in approximately 3600 seconds.
Remember that the timeout value is expressed in minutes.
If you need a higher expiration time for your sessions,
set timeout= in <sessionState to 120, if that's what you need.
If you do, the sessions will expire in 7200 seconds.
Take note that the larger the session expiration time,
the more memory consumption and that, at some point,
you might wind up with a recycled application due to
lack of sufficient RAM, and all your sessions will expire anyway.
You will have to experiment and look for a trade-off between
configured session expiration time and application recycling time.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:uT******** ******@TK2MSFTN GP09.phx.gbl...
Hello,
i'm struggling with a somehow badly understood session scenario.
I provide acces to my pages based on form authentication using
Session cookies.
Som of my pages are supposed to be running continuously and refreshing
once an hour.
I there set timeout= 61 in <sessionState section and on my page it
says
<meta http-equiv="refresh" content="3600"> .
I also set timeout=120 in the <forms section of web.config to make sure
the cookie does not expire before the session has been renewed.
But anyway i'm getting the temeout every 3600 seconds.
Can someone explain this?
Many thanks in advance.
JB
in my case i want to do a refresh every hour (<meta http-equiv="refresh"
content="3600"> ).so i set timeout=61. But this fails unexpectedely.
Why?
can i have session tiemout=20 when
"Juan T. Llibre" <no***********@ nowhere.com> wrote in message
news:e0******** ******@TK2MSFTN GP15.phx.gbl... The refresh time is immaterial.
If you have your session timeout set to 20 minutes,
and have a meta refresh, in all your pages, set to 19 minutes,
you could have your sessions continually refreshed, without the
need to accumulate RAM resources over 120 minutes.
As long as a user has a page at your site open, the sessions
would be automatically extended for another 20 minutes.
If they close all pages at your site, i.e., if they go away
permanently, then the sessions would expire 20 minutes
after the last page open was refreshed.
There's really no need to have large session timeout values.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:e%******** ********@TK2MSF TNGP15.phx.gbl. .. But then how do i avoid my session to timeout still keeping the refresh
time to 1 hour (3600 seconds)?
"Juan T. Llibre" <no***********@ nowhere.com> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. .. Actually, it makes a lot of sense that, if you have
timeout= 61 in <sessionState , that the sessions
would expire in approximately 3600 seconds.
Remember that the timeout value is expressed in minutes.
If you need a higher expiration time for your sessions,
set timeout= in <sessionState to 120, if that's what you need.
If you do, the sessions will expire in 7200 seconds.
Take note that the larger the session expiration time,
the more memory consumption and that, at some point,
you might wind up with a recycled application due to
lack of sufficient RAM, and all your sessions will expire anyway.
You will have to experiment and look for a trade-off between
configured session expiration time and application recycling time.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:uT******** ******@TK2MSFTN GP09.phx.gbl...
Hello,
i'm struggling with a somehow badly understood session scenario.
I provide acces to my pages based on form authentication using
Session cookies.
Som of my pages are supposed to be running continuously and refreshing
once an hour.
I there set timeout= 61 in <sessionState section and on my page it
says
<meta http-equiv="refresh" content="3600"> .
I also set timeout=120 in the <forms section of web.config to make sure
the cookie does not expire before the session has been renewed.
But anyway i'm getting the temeout every 3600 seconds.
Can someone explain this?
Many thanks in advance.
JB
Are you using out-of-process session state managemenet ?
( State Server or SQL Server ? )
If you are, Session_OnEnd might not get called.
Session_OnEnd only gets called if using InProc
( in-process ) session state management.
With SQL Server, there's a way to clean up
the expired sessions by running a SQL job.
Juan T. Llibre
ASP.NET MVP http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:un******** ******@TK2MSFTN GP10.phx.gbl... in my case i want to do a refresh every hour (<meta http-equiv="refresh"
content="3600"> ).so i set timeout=61. But this fails unexpectedely.
Why?
can i have session tiemout=20 when
"Juan T. Llibre" <no***********@ nowhere.com> wrote in message
news:e0******** ******@TK2MSFTN GP15.phx.gbl... The refresh time is immaterial.
If you have your session timeout set to 20 minutes,
and have a meta refresh, in all your pages, set to 19 minutes,
you could have your sessions continually refreshed, without the
need to accumulate RAM resources over 120 minutes.
As long as a user has a page at your site open, the sessions
would be automatically extended for another 20 minutes.
If they close all pages at your site, i.e., if they go away
permanently, then the sessions would expire 20 minutes
after the last page open was refreshed.
There's really no need to have large session timeout values.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:e%******** ********@TK2MSF TNGP15.phx.gbl. .. But then how do i avoid my session to timeout still keeping the refresh
time to 1 hour (3600 seconds)?
"Juan T. Llibre" <no***********@ nowhere.com> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..
Actually, it makes a lot of sense that, if you have
timeout= 61 in <sessionState , that the sessions
would expire in approximately 3600 seconds.
Remember that the timeout value is expressed in minutes.
If you need a higher expiration time for your sessions,
set timeout= in <sessionState to 120, if that's what you need.
If you do, the sessions will expire in 7200 seconds.
Take note that the larger the session expiration time,
the more memory consumption and that, at some point,
you might wind up with a recycled application due to
lack of sufficient RAM, and all your sessions will expire anyway.
You will have to experiment and look for a trade-off between
configured session expiration time and application recycling time.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:uT******** ******@TK2MSFTN GP09.phx.gbl...
>
> Hello,
> i'm struggling with a somehow badly understood session scenario.
> I provide acces to my pages based on form authentication using
> Session cookies.
>
> Som of my pages are supposed to be running continuously and refreshing
> once an hour.
> I there set timeout= 61 in <sessionState section and on my page it
> says
> <meta http-equiv="refresh" content="3600"> .
> I also set timeout=120 in the <forms section of web.config to make
> sure
> the cookie does not expire before the session has been renewed.
>
> But anyway i'm getting the temeout every 3600 seconds.
> Can someone explain this?
>
> Many thanks in advance.
>
> JB
>
>
>
>
>
No i'm not using out of process session.
"Juan T. Llibre" <no***********@ nowhere.com> wrote in message
news:OR******** ******@TK2MSFTN GP10.phx.gbl... Are you using out-of-process session state managemenet ?
( State Server or SQL Server ? )
If you are, Session_OnEnd might not get called.
Session_OnEnd only gets called if using InProc
( in-process ) session state management.
With SQL Server, there's a way to clean up
the expired sessions by running a SQL job.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:un******** ******@TK2MSFTN GP10.phx.gbl... in my case i want to do a refresh every hour (<meta http-equiv="refresh"
content="3600"> ).so i set timeout=61. But this fails unexpectedely.
Why?
can i have session tiemout=20 when
"Juan T. Llibre" <no***********@ nowhere.com> wrote in message
news:e0******** ******@TK2MSFTN GP15.phx.gbl... The refresh time is immaterial.
If you have your session timeout set to 20 minutes,
and have a meta refresh, in all your pages, set to 19 minutes,
you could have your sessions continually refreshed, without the
need to accumulate RAM resources over 120 minutes.
As long as a user has a page at your site open, the sessions
would be automatically extended for another 20 minutes.
If they close all pages at your site, i.e., if they go away
permanently, then the sessions would expire 20 minutes
after the last page open was refreshed.
There's really no need to have large session timeout values.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:e%******** ********@TK2MSF TNGP15.phx.gbl. ..
But then how do i avoid my session to timeout still keeping the refresh
time to 1 hour (3600 seconds)?
"Juan T. Llibre" <no***********@ nowhere.com> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..
> Actually, it makes a lot of sense that, if you have
> timeout= 61 in <sessionState , that the sessions
> would expire in approximately 3600 seconds.
>
> Remember that the timeout value is expressed in minutes.
>
> If you need a higher expiration time for your sessions,
> set timeout= in <sessionState to 120, if that's what you need.
>
> If you do, the sessions will expire in 7200 seconds.
>
> Take note that the larger the session expiration time,
> the more memory consumption and that, at some point,
> you might wind up with a recycled application due to
> lack of sufficient RAM, and all your sessions will expire anyway.
>
> You will have to experiment and look for a trade-off between
> configured session expiration time and application recycling time.
>
>
>
> Juan T. Llibre
> ASP.NET MVP
> http://asp.net.do/foros/
> Foros de ASP.NET en Español
> Ven, y hablemos de ASP.NET...
> =============== =======
>
> "jensen bredal" <je***********@ yahoo.dk> wrote in message
> news:uT******** ******@TK2MSFTN GP09.phx.gbl...
>>
>> Hello,
>> i'm struggling with a somehow badly understood session scenario.
>> I provide acces to my pages based on form authentication using
>> Session cookies.
>>
>> Som of my pages are supposed to be running continuously and
>> refreshing once an hour.
>> I there set timeout= 61 in <sessionState section and on my page
>> it says
>> <meta http-equiv="refresh" content="3600"> .
>> I also set timeout=120 in the <forms section of web.config to make
>> sure
>> the cookie does not expire before the session has been renewed.
>>
>> But anyway i'm getting the temeout every 3600 seconds.
>> Can someone explain this?
>>
>> Many thanks in advance.
>>
>> JB
>>
>>
>>
>>
>>
>
>
I'd suggest you test with smaller values,
so that you can run a number of tests
to check whether it runs OK or not.
Try setting timeout to 1 and refresh to 2.
That will allow you to test faster.
Then, depending on the results, you can increment.
If I recall correctly, the maximum session
timeout value is 1440 minutes, or 24 hours.
Anything higher than that will throw an error.
Juan T. Llibre
ASP.NET MVP http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. .. No i'm not using out of process session.
"Juan T. Llibre" <no***********@ nowhere.com> wrote in message
news:OR******** ******@TK2MSFTN GP10.phx.gbl... Are you using out-of-process session state managemenet ?
( State Server or SQL Server ? )
If you are, Session_OnEnd might not get called.
Session_OnEnd only gets called if using InProc
( in-process ) session state management.
With SQL Server, there's a way to clean up
the expired sessions by running a SQL job.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:un******** ******@TK2MSFTN GP10.phx.gbl... in my case i want to do a refresh every hour (<meta http-equiv="refresh"
content="3600"> ).so i set timeout=61. But this fails unexpectedely.
Why?
can i have session tiemout=20 when
"Juan T. Llibre" <no***********@ nowhere.com> wrote in message
news:e0******** ******@TK2MSFTN GP15.phx.gbl...
The refresh time is immaterial.
If you have your session timeout set to 20 minutes,
and have a meta refresh, in all your pages, set to 19 minutes,
you could have your sessions continually refreshed, without the
need to accumulate RAM resources over 120 minutes.
As long as a user has a page at your site open, the sessions
would be automatically extended for another 20 minutes.
If they close all pages at your site, i.e., if they go away
permanently, then the sessions would expire 20 minutes
after the last page open was refreshed.
There's really no need to have large session timeout values.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:e%******** ********@TK2MSF TNGP15.phx.gbl. ..
> But then how do i avoid my session to timeout still keeping the
> refresh
> time to 1 hour (3600 seconds)?
>
>
>
> "Juan T. Llibre" <no***********@ nowhere.com> wrote in message
> news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..
>> Actually, it makes a lot of sense that, if you have
>> timeout= 61 in <sessionState , that the sessions
>> would expire in approximately 3600 seconds.
>>
>> Remember that the timeout value is expressed in minutes.
>>
>> If you need a higher expiration time for your sessions,
>> set timeout= in <sessionState to 120, if that's what you need.
>>
>> If you do, the sessions will expire in 7200 seconds.
>>
>> Take note that the larger the session expiration time,
>> the more memory consumption and that, at some point,
>> you might wind up with a recycled application due to
>> lack of sufficient RAM, and all your sessions will expire anyway.
>>
>> You will have to experiment and look for a trade-off between
>> configured session expiration time and application recycling time.
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> http://asp.net.do/foros/
>> Foros de ASP.NET en Español
>> Ven, y hablemos de ASP.NET...
>> =============== =======
>>
>> "jensen bredal" <je***********@ yahoo.dk> wrote in message
>> news:uT******** ******@TK2MSFTN GP09.phx.gbl...
>>>
>>> Hello,
>>> i'm struggling with a somehow badly understood session scenario.
>>> I provide acces to my pages based on form authentication using
>>> Session cookies.
>>>
>>> Som of my pages are supposed to be running continuously and
>>> refreshing once an hour.
>>> I there set timeout= 61 in <sessionState section and on my page
>>> it says
>>> <meta http-equiv="refresh" content="3600"> .
>>> I also set timeout=120 in the <forms section of web.config to make
>>> sure
>>> the cookie does not expire before the session has been renewed.
>>>
>>> But anyway i'm getting the temeout every 3600 seconds.
>>> Can someone explain this?
>>>
>>> Many thanks in advance.
>>>
>>> JB
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
Strangely there is no problem with small values up to about 30 minutes!
i tried 1 , 2 , 15 .....30. No timeout or what so ever.
"Juan T. Llibre" <no***********@ nowhere.com> wrote in message
news:OU******** ******@TK2MSFTN GP14.phx.gbl... I'd suggest you test with smaller values,
so that you can run a number of tests
to check whether it runs OK or not.
Try setting timeout to 1 and refresh to 2.
That will allow you to test faster.
Then, depending on the results, you can increment.
If I recall correctly, the maximum session
timeout value is 1440 minutes, or 24 hours.
Anything higher than that will throw an error.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. .. No i'm not using out of process session.
"Juan T. Llibre" <no***********@ nowhere.com> wrote in message
news:OR******** ******@TK2MSFTN GP10.phx.gbl... Are you using out-of-process session state managemenet ?
( State Server or SQL Server ? )
If you are, Session_OnEnd might not get called.
Session_OnEnd only gets called if using InProc
( in-process ) session state management.
With SQL Server, there's a way to clean up
the expired sessions by running a SQL job.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:un******** ******@TK2MSFTN GP10.phx.gbl...
in my case i want to do a refresh every hour (<meta
http-equiv="refresh" content="3600"> ).so i set timeout=61. But this
fails unexpectedely.
Why?
can i have session tiemout=20 when
"Juan T. Llibre" <no***********@ nowhere.com> wrote in message
news:e0******** ******@TK2MSFTN GP15.phx.gbl...
> The refresh time is immaterial.
>
> If you have your session timeout set to 20 minutes,
> and have a meta refresh, in all your pages, set to 19 minutes,
> you could have your sessions continually refreshed, without the
> need to accumulate RAM resources over 120 minutes.
>
> As long as a user has a page at your site open, the sessions
> would be automatically extended for another 20 minutes.
>
> If they close all pages at your site, i.e., if they go away
> permanently, then the sessions would expire 20 minutes
> after the last page open was refreshed.
>
> There's really no need to have large session timeout values.
>
>
>
>
> Juan T. Llibre
> ASP.NET MVP
> http://asp.net.do/foros/
> Foros de ASP.NET en Español
> Ven, y hablemos de ASP.NET...
> =============== =======
>
> "jensen bredal" <je***********@ yahoo.dk> wrote in message
> news:e%******** ********@TK2MSF TNGP15.phx.gbl. ..
>> But then how do i avoid my session to timeout still keeping the
>> refresh
>> time to 1 hour (3600 seconds)?
>>
>>
>>
>> "Juan T. Llibre" <no***********@ nowhere.com> wrote in message
>> news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..
>>> Actually, it makes a lot of sense that, if you have
>>> timeout= 61 in <sessionState , that the sessions
>>> would expire in approximately 3600 seconds.
>>>
>>> Remember that the timeout value is expressed in minutes.
>>>
>>> If you need a higher expiration time for your sessions,
>>> set timeout= in <sessionState to 120, if that's what you need.
>>>
>>> If you do, the sessions will expire in 7200 seconds.
>>>
>>> Take note that the larger the session expiration time,
>>> the more memory consumption and that, at some point,
>>> you might wind up with a recycled application due to
>>> lack of sufficient RAM, and all your sessions will expire anyway.
>>>
>>> You will have to experiment and look for a trade-off between
>>> configured session expiration time and application recycling time.
>>>
>>>
>>>
>>> Juan T. Llibre
>>> ASP.NET MVP
>>> http://asp.net.do/foros/
>>> Foros de ASP.NET en Español
>>> Ven, y hablemos de ASP.NET...
>>> =============== =======
>>>
>>> "jensen bredal" <je***********@ yahoo.dk> wrote in message
>>> news:uT******** ******@TK2MSFTN GP09.phx.gbl...
>>>>
>>>> Hello,
>>>> i'm struggling with a somehow badly understood session scenario.
>>>> I provide acces to my pages based on form authentication using
>>>> Session cookies.
>>>>
>>>> Som of my pages are supposed to be running continuously and
>>>> refreshing once an hour.
>>>> I there set timeout= 61 in <sessionState section and on my page
>>>> it says
>>>> <meta http-equiv="refresh" content="3600"> .
>>>> I also set timeout=120 in the <forms section of web.config to make
>>>> sure
>>>> the cookie does not expire before the session has been renewed.
>>>>
>>>> But anyway i'm getting the temeout every 3600 seconds.
>>>> Can someone explain this?
>>>>
>>>> Many thanks in advance.
>>>>
>>>> JB
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
re: Strangely there is no problem with small values up to about 30 minutes!
That's not strange at all, if the maximum session
timeout value is 1440 minutes, or 24 hours,
as explained in my last message.
Anything higher than that will throw an error.
Sorry for not remembering that figure earlier.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:%2******** ********@TK2MSF TNGP14.phx.gbl. .. Strangely there is no problem with small values up to about 30 minutes!
i tried 1 , 2 , 15 .....30. No timeout or what so ever.
"Juan T. Llibre" <no***********@ nowhere.com> wrote in message
news:OU******** ******@TK2MSFTN GP14.phx.gbl... I'd suggest you test with smaller values,
so that you can run a number of tests
to check whether it runs OK or not.
Try setting timeout to 1 and refresh to 2.
That will allow you to test faster.
Then, depending on the results, you can increment.
If I recall correctly, the maximum session
timeout value is 1440 minutes, or 24 hours.
Anything higher than that will throw an error.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. .. No i'm not using out of process session.
"Juan T. Llibre" <no***********@ nowhere.com> wrote in message
news:OR******** ******@TK2MSFTN GP10.phx.gbl...
Are you using out-of-process session state managemenet ?
( State Server or SQL Server ? )
If you are, Session_OnEnd might not get called.
Session_OnEnd only gets called if using InProc
( in-process ) session state management.
With SQL Server, there's a way to clean up
the expired sessions by running a SQL job.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"jensen bredal" <je***********@ yahoo.dk> wrote in message
news:un******** ******@TK2MSFTN GP10.phx.gbl...
> in my case i want to do a refresh every hour (<meta
> http-equiv="refresh" content="3600"> ).so i set timeout=61. But this
> fails unexpectedely.
> Why?
>
>
>
> can i have session tiemout=20 when
> "Juan T. Llibre" <no***********@ nowhere.com> wrote in message
> news:e0******** ******@TK2MSFTN GP15.phx.gbl...
>> The refresh time is immaterial.
>>
>> If you have your session timeout set to 20 minutes,
>> and have a meta refresh, in all your pages, set to 19 minutes,
>> you could have your sessions continually refreshed, without the
>> need to accumulate RAM resources over 120 minutes.
>>
>> As long as a user has a page at your site open, the sessions
>> would be automatically extended for another 20 minutes.
>>
>> If they close all pages at your site, i.e., if they go away
>> permanently, then the sessions would expire 20 minutes
>> after the last page open was refreshed.
>>
>> There's really no need to have large session timeout values.
>>
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> http://asp.net.do/foros/
>> Foros de ASP.NET en Español
>> Ven, y hablemos de ASP.NET...
>> =============== =======
>>
>> "jensen bredal" <je***********@ yahoo.dk> wrote in message
>> news:e%******** ********@TK2MSF TNGP15.phx.gbl. ..
>>> But then how do i avoid my session to timeout still keeping the
>>> refresh
>>> time to 1 hour (3600 seconds)?
>>>
>>>
>>>
>>> "Juan T. Llibre" <no***********@ nowhere.com> wrote in message
>>> news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..
>>>> Actually, it makes a lot of sense that, if you have
>>>> timeout= 61 in <sessionState , that the sessions
>>>> would expire in approximately 3600 seconds.
>>>>
>>>> Remember that the timeout value is expressed in minutes.
>>>>
>>>> If you need a higher expiration time for your sessions,
>>>> set timeout= in <sessionState to 120, if that's what you need.
>>>>
>>>> If you do, the sessions will expire in 7200 seconds.
>>>>
>>>> Take note that the larger the session expiration time,
>>>> the more memory consumption and that, at some point,
>>>> you might wind up with a recycled application due to
>>>> lack of sufficient RAM, and all your sessions will expire anyway.
>>>>
>>>> You will have to experiment and look for a trade-off between
>>>> configured session expiration time and application recycling time.
>>>>
>>>>
>>>>
>>>> Juan T. Llibre
>>>> ASP.NET MVP
>>>> http://asp.net.do/foros/
>>>> Foros de ASP.NET en Español
>>>> Ven, y hablemos de ASP.NET...
>>>> =============== =======
>>>>
>>>> "jensen bredal" <je***********@ yahoo.dk> wrote in message
>>>> news:uT******** ******@TK2MSFTN GP09.phx.gbl...
>>>>>
>>>>> Hello,
>>>>> i'm struggling with a somehow badly understood session scenario.
>>>>> I provide acces to my pages based on form authentication using
>>>>> Session cookies.
>>>>>
>>>>> Som of my pages are supposed to be running continuously and
>>>>> refreshing once an hour.
>>>>> I there set timeout= 61 in <sessionState section and on my
>>>>> page it says
>>>>> <meta http-equiv="refresh" content="3600"> .
>>>>> I also set timeout=120 in the <forms section of web.config to make
>>>>> sure
>>>>> the cookie does not expire before the session has been renewed.
>>>>>
>>>>> But anyway i'm getting the temeout every 3600 seconds.
>>>>> Can someone explain this?
>>>>>
>>>>> Many thanks in advance.
>>>>>
>>>>> JB
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics | |
by: Don Nelson |
last post by:
hi,
I am using SQL server 2000.and trying to resolve a deadlock issue.For
this i am looking at SQL profiler.and while turning the trace on, i
select Lock:Timeout event that needs to be traced.When done so, and
executing other requests, there appears an entry which just mentions
spid number, text data field is empty. I would like to know if...
|
by: Sachin Jagtap |
last post by:
Hi,
I am getting exception while poping item from queue, I am writing
messages coming from client in a queue in one thread and then in other
thread i am reading from queue and writing in file.
I have not implemented any syncronization between reading and
wrinting, just i checking size of queue, if it is not empty i am
reading from queue...
|
by: WantedToBeDBA |
last post by:
Hi all,
We have db2 installed on AIX box (db2 version - 8.1). Its started
and i am able to view 50000(default port) in netstat(netstat -a -n).
But when i try to connect using telnet, i am getting this error. I
don't know how to correct it.
Till yesterday its working well. I don't know what is the problem
now..
Help me guys. Its very...
|
by: Niloday |
last post by:
Hi All,
I have developed a web service and deployed it on the Win2000 box. I can
access the web methods of this web service when my client application is
debugged from VS.NET studio. But it fails with an 'Operation Timeout'
exception when run from the compiled version. The client application is a
windows forms application.
The...
|
by: B0nj |
last post by:
I have got a web application that now doesn't use session state after I eliminated all session variables, opting to banish them all to the querystring for better performance
I have turned sessionState "off" in the web.config file, however it won't let me debug when it is off
Is this by design? I can understand how it may need session in order...
| | |
by: Daniel |
last post by:
Hi,
i'm using the session in my project and each user will be given the access
based on his role.
On my computer i try to run the program, the session works fine.
The problem occurs when i try to access the same program at the same time
from another computer that connected to my pc.
The session cannot identify both of the user's role, it...
|
by: amjad |
last post by:
Unable to use SQL Server because ASP.NET version 2.0 Session State is not
installed on the SQL server
this error i get when i tried to run my application and want to use sql
server to store session state.
any body know any information about it how to setup session state variable.
as i have another application in which its not working. i dont...
|
by: Hemant Pathak |
last post by:
Hi All
i have develop a software(Customer Service Managment System) front end is VB 6.0 and Back end is SQL 2000 i want to run this software is Server System and Client System the how can i do this.
please urgent...........
|
by: ruchikagupta |
last post by:
i have a grid view with two select command buttons and i want to track which one is clicked how can i do tht can any1 plz help its really urgent
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed.
This is as boiled down as I can make it. ...
| | |
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one.
At the time of converting from word file to html my equations which are in the word document file was convert...
|
by: TSSRALBI |
last post by:
Hello
I'm a network technician in training and I need your help.
I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs.
The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols.
I succeeded, with both firewalls in...
|
by: adsilva |
last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
| | |
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
| |
