By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,963 Members | 1,276 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,963 IT Pros & Developers. It's quick & easy.

Avoid Application Timeout

P: n/a
Hi,
How can I avoid application timeout? Generally a web application time out is
20 minutes, however, we can define this timeout in web.config to any number
of minutes. After giving 500 minutes of time out which is about little more
than 8 hours, the page expires in less than 2 hours. I am confused here how
to avoid this timeout problem.

I just dont want my page to be expired, should work similar to windows
application.
Possible?

Regards,
Atul
Jul 3 '07 #1
Share this Question
Share on Google+
10 Replies


P: n/a
Hello Atul,

Set the "0" and the session never timeout.
But this perhaps leads you to the problem with your resources.
Each session takes certain amount of system resources and free then when
timeout, and in your case resources never be releases back

---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

ASHi,
ASHow can I avoid application timeout? Generally a web application
AStime out is
AS20 minutes, however, we can define this timeout in web.config to any
ASnumber
ASof minutes. After giving 500 minutes of time out which is about
ASlittle more
ASthan 8 hours, the page expires in less than 2 hours. I am confused
AShere how
ASto avoid this timeout problem.
ASI just dont want my page to be expired, should work similar to
ASwindows
ASapplication.
ASPossible?
ASRegards,
ASAtul
Jul 3 '07 #2

P: n/a
Set the "0" and the session never timeout.

Are you sure about that? Non-expiring sessions on a busy site would bring
it down. The reason long sessions still expire is cos the application is
inactive so gets torn down regardless of your active sessions.
Jul 3 '07 #3

P: n/a
Hello Aidy,

Yep, kinda wrong :( Sorry.

Seems that there is no way to have the non-timeout session.
in .NET 2.0 the limited the session by 525,601 minutes (1 year)

---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo
>Set the "0" and the session never timeout.
AAre you sure about that? Non-expiring sessions on a busy site would
Abring it down. The reason long sessions still expire is cos the
Aapplication is inactive so gets torn down regardless of your active
Asessions.
A>
Jul 3 '07 #4

P: n/a
That's still quite high, near as damn it never expiring.

"Michael Nemtsev" <ne*****@msn.comwrote in message
news:a2***************************@msnews.microsof t.com...
Hello Aidy,

Yep, kinda wrong :( Sorry.

Seems that there is no way to have the non-timeout session.
in .NET 2.0 the limited the session by 525,601 minutes (1 year)

---
WBR, Michael Nemtsev [.NET/C# MVP]. My blog:
http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo
>>Set the "0" and the session never timeout.
AAre you sure about that? Non-expiring sessions on a busy site would
Abring it down. The reason long sessions still expire is cos the
Aapplication is inactive so gets torn down regardless of your active
Asessions.
A>

Jul 3 '07 #5

P: n/a
Thanks for input!
So what is the timeout precedence? Whether IIS works as per the settings
defined in the IIS or in web.config? As per my understanding, web.config's
timeout got higher precedence over IIS timeout settings. What do you say?
"Aidy" <ai**@noemail.xxxa.comwrote in message
news:T_******************************@bt.com...
That's still quite high, near as damn it never expiring.

"Michael Nemtsev" <ne*****@msn.comwrote in message
news:a2***************************@msnews.microsof t.com...
>Hello Aidy,

Yep, kinda wrong :( Sorry.

Seems that there is no way to have the non-timeout session.
in .NET 2.0 the limited the session by 525,601 minutes (1 year)

---
WBR, Michael Nemtsev [.NET/C# MVP]. My blog:
http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and
we miss it, but that it is too low and we reach it" (c) Michelangelo
>>>Set the "0" and the session never timeout.
AAre you sure about that? Non-expiring sessions on a busy site would
Abring it down. The reason long sessions still expire is cos the
Aapplication is inactive so gets torn down regardless of your active
Asessions.
A>


Jul 3 '07 #6

P: n/a
Hello Atul,

IIS just translate your web.config in GUI representation.

---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

ASThanks for input!
ASSo what is the timeout precedence? Whether IIS works as per the
ASsettings
ASdefined in the IIS or in web.config? As per my understanding,
ASweb.config's
AStimeout got higher precedence over IIS timeout settings. What do you
ASsay?
AS"Aidy" <ai**@noemail.xxxa.comwrote in message
ASnews:T_******************************@bt.com...
AS>
>That's still quite high, near as damn it never expiring.

"Michael Nemtsev" <ne*****@msn.comwrote in message
news:a2***************************@msnews.microso ft.com...
>>Hello Aidy,

Yep, kinda wrong :( Sorry.

Seems that there is no way to have the non-timeout session. in .NET
2.0 the limited the session by 525,601 minutes (1 year)

---
WBR, Michael Nemtsev [.NET/C# MVP]. My blog:
http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/
"The greatest danger for most of us is not that our aim is too high
and we miss it, but that it is too low and we reach it" (c)
Michelangelo

Set the "0" and the session never timeout.
>
AAre you sure about that? Non-expiring sessions on a busy site
would
Abring it down. The reason long sessions still expire is cos the
Aapplication is inactive so gets torn down regardless of your
active
Asessions.
A>

Jul 3 '07 #7

P: n/a
Take a look at my article on codeproject "Make session last forever"
http://www.codeproject.com/useritems/SessionForever.asp
Hope it's going to help.

George.

"Atul Shukla" <py*****@gmail.comwrote in message
news:Of**************@TK2MSFTNGP04.phx.gbl...
Hi,
How can I avoid application timeout? Generally a web application time out
is 20 minutes, however, we can define this timeout in web.config to any
number of minutes. After giving 500 minutes of time out which is about
little more than 8 hours, the page expires in less than 2 hours. I am
confused here how to avoid this timeout problem.

I just dont want my page to be expired, should work similar to windows
application.
Possible?

Regards,
Atul


Jul 3 '07 #8

P: n/a
there are two timeouts. session timeout and application timeout. if
asp.net is not used for its timeout period, then its shutdown. ou an
bump this up, but recycles ca still happen (say too many inproc sessions).

if you want your page to not timeout, switch to sqlserver session, and
set the session timeout to a couple days (or as long as you want). then
your users will never see lost sessions from recycles. you can even make
the session cookie persistent so that it lasts weeks (handy for a
shopping cart application)

-- bruce (sqlwork.com)

Atul Shukla wrote:
Hi,
How can I avoid application timeout? Generally a web application time out is
20 minutes, however, we can define this timeout in web.config to any number
of minutes. After giving 500 minutes of time out which is about little more
than 8 hours, the page expires in less than 2 hours. I am confused here how
to avoid this timeout problem.

I just dont want my page to be expired, should work similar to windows
application.
Possible?

Regards,
Atul

Jul 3 '07 #9

P: n/a
Hi Bruce,

Thanks!

Storing session values in SQL is good idea. I was thinking to avoid using
Session variables in the application. So will store minimum information in
cookies (encrypted form). I am in doubt, thinking that even though if I dont
use Session Variables, would application/browser session expire?
Regards,
Atul

"bruce barker" <no****@nospam.comwrote in message
news:e1*************@TK2MSFTNGP05.phx.gbl...
there are two timeouts. session timeout and application timeout. if
asp.net is not used for its timeout period, then its shutdown. ou an bump
this up, but recycles ca still happen (say too many inproc sessions).

if you want your page to not timeout, switch to sqlserver session, and set
the session timeout to a couple days (or as long as you want). then your
users will never see lost sessions from recycles. you can even make the
session cookie persistent so that it lasts weeks (handy for a shopping
cart application)

-- bruce (sqlwork.com)

Atul Shukla wrote:
>Hi,
How can I avoid application timeout? Generally a web application time out
is 20 minutes, however, we can define this timeout in web.config to any
number of minutes. After giving 500 minutes of time out which is about
little more than 8 hours, the page expires in less than 2 hours. I am
confused here how to avoid this timeout problem.

I just dont want my page to be expired, should work similar to windows
application.
Possible?

Regards,
Atul
Jul 5 '07 #10

P: n/a
Actually I want to keep the session active for more than 8 hours. So what I
did is that changed the IIS Enable Session Timeout setting to 500 minutes,
also disabled all the checkboxes given in the Recycle Tab for an application
pool. Another check box is on Performance tab named as 'idle timeout', I
disabled it too (though not recommended and planning to put 510 minutes if
idle for more than timeout to release the resources). And it has solved my
problem for the time being.

"bruce barker" <no****@nospam.comwrote in message
news:e1*************@TK2MSFTNGP05.phx.gbl...
there are two timeouts. session timeout and application timeout. if
asp.net is not used for its timeout period, then its shutdown. ou an bump
this up, but recycles ca still happen (say too many inproc sessions).

if you want your page to not timeout, switch to sqlserver session, and set
the session timeout to a couple days (or as long as you want). then your
users will never see lost sessions from recycles. you can even make the
session cookie persistent so that it lasts weeks (handy for a shopping
cart application)

-- bruce (sqlwork.com)

Atul Shukla wrote:
>Hi,
How can I avoid application timeout? Generally a web application time out
is 20 minutes, however, we can define this timeout in web.config to any
number of minutes. After giving 500 minutes of time out which is about
little more than 8 hours, the page expires in less than 2 hours. I am
confused here how to avoid this timeout problem.

I just dont want my page to be expired, should work similar to windows
application.
Possible?

Regards,
Atul
Jul 10 '07 #11

This discussion thread is closed

Replies have been disabled for this discussion.