Problem with Session.Timeout in ASP Classic

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • thig95
    New Member
    • Nov 2007
    • 6

    Problem with Session.Timeout in ASP Classic

    Hi,

    I've got a web application written in ASP class with VBScript. We have a home grown conctact management system for my company that our users stay active in throughout the day. My problem lies with the continued timeout we sometimes experience.

    I have tried just about everything to allow an 8 hour timeout for this application. I've set the session timeout to 480 in IIS (running IIS 6 on windows 2k3 SE) and i've also tried coding it in our logon script session.timeout =480 but our users still timeout if inactive for 20 minutes. This seems to sometimes vary, but it is hard to determine exactly when the session variables are getting dumped. I've also checked the Metabase directly to make sure the settings from IIS are saving appropriately.

    The way I check to see if a user has timeout our or not is by running a vbscript at page load to see if session("isLogg edIn")="Y". If it is, the session state is still intact and the user carries on, or if it's empty they are redirected back to the logon page. The "isLoggedIn " session variable is only assigned at logon so I know it's not being overwritten, same with session.timeout .

    This has been driving me (and my users) absolutely crazy, so I am desperate for a little help. Any ideas if I may have missed something?

    ~Brian
  • urstop
    New Member
    • Oct 2007
    • 12

    #2
    Apart from that, there are other things to take care of for this to work,

    Check the IIS settings for Worker Process Recycling interval, and Idle recycling interval, you will have to play around this settings, because when the worker process recycles you will loose all your session data.

    Take a look and let me know what you find.

    Regards,
    UrStop

    Comment

    • thig95
      New Member
      • Nov 2007
      • 6

      #3
      Alright, I checked the settings on the DefaultAppPool and Recycle Worker Processes is checked with the time interval set to 1740 minutes. Now this wasn't something i set, so i am assuming that's the default value? Idle timeout for worker processes is 20 minutes. That might be the culprit...i'm going to change it to match the session state timeout and see if that helps. I'll let you!

      And THANK YOU for helping me with this, i've pulled out way too much of my hair over this...

      ~Brian

      Comment

      • thig95
        New Member
        • Nov 2007
        • 6

        #4
        Just went out to lunch for an hour, came back and sure enough i was knocked back to the logon page....

        Here's a little more background on the application's overall setup. We're accessing the site via SSL over port 443. As mentioned before, the server is a windows 2K3 SE with IIS 6.0. I have also deployed URL scan for enhanced security for our application. The site has a backend DB (MSSQL 2000) where all our relevant data is housed. Everything is in ASP classic, and no .NET is being used. I do have .NET 2.0 installed, as it was installed with the deployment of SP2.

        Are there any other settings in IIS or within ASP's native functions that could be causing my session variables to be dumped? The problem is also not browser specific, as i've noticed this via IE7 (primary browser used by our users) and FireFox 2.0.0.10 (used in testing/developement)

        ~Brian

        Comment

        • jhardman
          Recognized Expert Specialist
          • Jan 2007
          • 3405

          #5
          Originally posted by thig95
          Just went out to lunch for an hour, came back and sure enough i was knocked back to the logon page....

          Here's a little more background on the application's overall setup. We're accessing the site via SSL over port 443. As mentioned before, the server is a windows 2K3 SE with IIS 6.0. I have also deployed URL scan for enhanced security for our application. The site has a backend DB (MSSQL 2000) where all our relevant data is housed. Everything is in ASP classic, and no .NET is being used. I do have .NET 2.0 installed, as it was installed with the deployment of SP2.

          Are there any other settings in IIS or within ASP's native functions that could be causing my session variables to be dumped? The problem is also not browser specific, as i've noticed this via IE7 (primary browser used by our users) and FireFox 2.0.0.10 (used in testing/developement)

          ~Brian
          SSL might restrict that natively. Do you have to do this secure?

          a simple fix that one of my webmails does is refresh certain pages after a few minutes. This could be done with an iframe for convenience.

          Jared

          Comment

          Working...