Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • dendam 2 posts 22 karma points
    Jul 06, 2011 @ 17:45
    dendam
    0

    Asp.net session variable timeout problem

    I'm using Umbraco (umbraco v 4.6.1 (Assembly version: 1.0.4029.25836)) with controls in asp.net (.net 4.0) on iis6, and have a sessionvariable that is gone after about 20-30 mins.

    I've tried everything I could find on the internet:

    My web.config contains:

    <add key="umbracoTimeOutInMinutes" value="120" />
    <sessionState mode="InProc" cookieless="false" timeout="120" />
    <httpRuntime requestValidationMode="2.0" maxRequestLength="204800" executionTimeout="3600" />
    <forms loginUrl="/subsidies/inlog.aspx" name=".ASPXFORMSAUTH" timeout="120" />
    <membership defaultProvider="MyMembershipProvider" userIsOnlineTimeWindow="121">

    Machine:

    c:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Config\web.config

    <system.web>
      <sessionState timeout="120" />

    Application pool:

    Recycle worker processes (in minutes) : 120

    Shutdown worker processes after being idle for (time in minutes): 120

    Website properties:

    Connection timeout: 120 seconds

    Home Directory > Configuration > Options > Application Configuration >

        * x Enable session state (enabled)
        * Session timeout: 120 minutes

    And still, a session variable is gone in about 20-30 minutes. Hopefully someone can help me....

     

     

  • dendam 2 posts 22 karma points
    Jul 11, 2011 @ 11:17
    dendam
    0

    I found the problem, and it's fixed now.

    The problem was the application pool recycle. When it did a recylce the session variables where gone (also saw this in the eventviewer).

    So disabled the recycle, and only recycle now once every day (night).

  • shadowxtc 1 post 21 karma points
    Jun 17, 2012 @ 02:49
    shadowxtc
    0

    Hate to bump an old topic but I'm using Umbraco 4.7.2 on Azure and had a similar problem where users would be mysteriously logged out - making the timeout changes noted above in web.config solved the problem.

  • This forum is in read-only mode while we transition to the new forum.

    You can continue this topic on the new forum by tapping the "Continue discussion" link below.

Please Sign in or register to post replies