Hang problem in ASP.Net application

[todd.freed]

Hi all,

I have recently encountered the following problem with my ASP.Net
application.

After deploying our site and people started using it alot, we
discovered that if a person were to browse the site for a time, then go
and do somethign else while leaving the browser open, when they come
back to the site, none of the buttons do anything. Basically the site
has just become stale and loses all interactivity. Closing the browser
and reopening fixes the problem; However it would be great to get this
issue fixed.

Any input appreciated.

[Peter Bromberg [C# MVP]]

This could be due to their Session expiring, or to ASP.NET process recycling,
or other issues.
There are a number of techniques for handling this including refreshing the
page programmatically at intervals, checking to see if there is a Session and
if not , redirecting the "returning after hiatus user" to the login page, and
others.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"to********@gmail.com" wrote:

Hi all,

I have recently encountered the following problem with my ASP.Net
application.

After deploying our site and people started using it alot, we
discovered that if a person were to browse the site for a time, then go
and do somethign else while leaving the browser open, when they come
back to the site, none of the buttons do anything. Basically the site
has just become stale and loses all interactivity. Closing the browser
and reopening fixes the problem; However it would be great to get this
issue fixed.

Any input appreciated.

[jacqueharper]

Sounds like a session end problem?? How long are users "doing something
else," and what is the session timeout for the application set to
(typical default is 20 minutes)?

Jacque

[todd.freed]

Thanks for the input guys.

One thing to keep in mind is we do not use the Session collection
anywhere in our application.

Time Away - 20 minutes seems about right, though im not sure exactly
when the problem occurs.

Redirecting to login is probably our best bet- if just resuming from
where yuo left off isnt possible.