Application keeps resetting

Discussion in 'ASP.NET / ASP.NET Core' started by mlawrence, Nov 20, 2003.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. mlawrence

    mlawrence

    Just signed up for services today, and so far I am happy with the speed. [:)]

    I do notice the .net application keeps resetting itself every couple minutes. As you know, this means all application and session variables are lost, and my users need to relogin to my website. As well, the next page served takes considerably longer.

    Can someone look into this and let me know what I need to do to stop it from happening?

    Thanks.
     
    mlawrence, Nov 20, 2003
    #1
  2. steurm

    steurm

    There is a way to overcome this ...
    A user-session is kept alive, as long as the time between two page request is less than 10 minutes. What I did, is including in the footer of my page a non visible iframe (1px by 1 px), that uses a metatag to refresh itself every 9 minutes and 45 seconds. The page which reloads itself is a tiny cached .aspx file. Since I use this, I no longer hear my visitors complain about timing out of sessions.

    Maybe it could help you.
    success

    --
    Steurm
    www.steurm.net/steurm
     
    steurm, Nov 21, 2003
    #2
  3. mlawrence

    mlawrence

    Thanks for the information, and the tip! It's not yet in production, so I'll see what happens once I have a steady stream of hits.

    Bruce, I take it you are tech support for the site?

    Martin
     
    mlawrence, Nov 21, 2003
    #3
  4. Bruce

    Bruce DiscountASP.NET Staff

    The web server hosting your site is a Windows 2003 server and the server
    is configured to recycle an idle process after 10 mins of inactivity. This
    generally do not create problem if a site is in production. Unlike other
    hosting companies, we run each website as it own unique process which
    provides many benefits. For example,

    - better security

    An individual IIS worker process runs with the same authentication, that
    means if multiple sites are sharing a process, user can easily write a
    script to steal your files (including database file and connection
    information)

    - better stability.

    When a user write a bad application (say with a infinite loop), it will only affect their site and will not cause others outage.


    quote:Originally posted by mlawrence

    Just signed up for services today, and so far I am happy with the speed. [:)]

    I do notice the .net application keeps resetting itself every couple minutes. As you know, this means all application and session variables are lost, and my users need to relogin to my website. As well, the next page served takes considerably longer.

    Can someone look into this and let me know what I need to do to stop it from happening?

    Thanks.
    </blockquote id="quote"></font id="quote">
     
    Bruce, Nov 21, 2003
    #4
  5. Bruce

    Bruce DiscountASP.NET Staff

    No. I do mostly development stuff but i understand the system well enough.

    quote:Originally posted by mlawrence

    Thanks for the information, and the tip! It's not yet in production, so I'll see what happens once I have a steady stream of hits.

    Bruce, I take it you are tech support for the site?

    Martin
    </blockquote id="quote"></font id="quote">
     
    Bruce, Nov 22, 2003
    #5
  6. georgeASP

    georgeASP

    Doesn't this approach prevent the Session timeout from working properly -- that is, now the session will never time out, so if a user leaves his window up overnight, the session will never time out and the process will never recycle.

    George
     
    georgeASP, Oct 6, 2004
    #6
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page