471,350 Members | 1,928 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,350 software developers and data experts.

Hang problem in ASP.Net application

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.

Dec 20 '05 #1
3 1372
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.

Dec 20 '05 #2
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

Dec 20 '05 #3
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.

Dec 20 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Mahesh | last post: by
5 posts views Thread by Ido Zur | last post: by
2 posts views Thread by Amir The Ruler | last post: by
reply views Thread by Ben | last post: by
reply views Thread by henrycortezwu | last post: by
reply views Thread by Jeff | last post: by
reply views Thread by XIAOLAOHU | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.