CODEWITHSUNDEEP
iis-7asp-classic
David Kroll
David Kroll

Reputation: 1

Classic ASP application hangs after sitting open in browser for long period of time

I have a classic ASP application that uses a SQL backend. The app used Access until earlier this week, when I changed it to try to resolve this problem, to no avail. The problem is that the users leave the site open in IE all day long, and may take an hour or more between uses. After it's been sitting open for a while, when they try to make a request, the site hangs and eventually shows "page can not be displayed". If they hit the back button, then refresh the page, it works fine.

I just changed the app pool from Integrated to Classic, so that might fix it, but if anyone has any other ideas, I welcome them. There is one other site on IIS (7.5) and while a user is experiencing this hang, there is no large resource usage on the server.

Also, I've turned on Failed Request Tracking for anything that runs over 3 seconds. I get log files when these hangs happen, but they say that the request returned status code 200, but it always seems to stop in the log at NOTIFY_MODULE_START - IsapiModule, Notification 128, Notification EXECUTE_REQUEST_HANDLER. The Module Notification for that event shows NO_END in the duration.

Thanks,

David

Upvotes: 0

Views: 600

Answers (2)

silver
silver

Reputation: 630

You could build a background AJAX / jquery pinger in Javascript that just pinged the server every 5 mins to refresh the session and you would never be logged out.

Upvotes: 1

John
John

Reputation: 4638

On IIS sessions time out after a set period - the default is 20 minutes.

What you could do is set a session variable on your landing page - eg 

<% Session("Active") = "yes" %>

Then have a script on all your other pages to bounce you back to the landing page if the session does time out - eg

<% if Session("Active") <> "yes" then 
Response.redirect("mylandingpage.asp")
end if %>

Upvotes: 0

Related Questions