Why session expire very quickly before given time in IIS - Visual Studio 2012

Question

0.00/5 (No votes)

See more:

I have facing a problem,
I have set session time out in web.config

XML

<system.web>
      <sessionState timeout="60" mode="InProc" />
    <httpRuntime targetFramework="4.5" />
    <compilation debug="true" targetFramework="4.5" />
    <authentication mode="Forms">
      <forms loginUrl="~/Account/Login" timeout="2880" />
    </authentication>
  </system.web>

In my controller

SQL

public ActionResult CreateBrand()
        {
            Session.Timeout=60;
            Purchase purchase = Session["purchaseItem"] as Purchase;
            if (purchase!=null && purchase.Brand != null)
            {
                return View(purchase.Brand);
            }
            return View();
        }

Any bode can tell me what is the problem with session. Why session expire very quickly, may be within just 1 i or 2 minutes?

Posted 8-Nov-13 16:49pm

Dotnet Specialist Hasnain

Add a Solution

Comments

Tadit Dash (ତଡିତ୍ କୁମାର ଦାଶ) 9-Nov-13 11:10am

Check IIS settings.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Juan Davel · Answer 1 · 2013-11-14T01:46:00

Do you absolutely need to use InProc? I suggest you either use (a) Session State Server or (b) SQL Server to manage your user sessions. I have not had one client complain about their session expiring after leaving their computer for 10-20 minutes, and we are using SQL Server to manage the user sessions. SQL Server-based sessions also survives application pool recycles.

Alternatively, and if you absolutely MUST use InProc, then you can try two different things: (a) Ensure your application pools' timeout is set correctly, and (b) implement something like an IFRAME that refreshes the user session automatically every few seconds or minutes ("Keep Alive").

First, try the IIS method:
- Open IIS
- Select Application Pools on the left side
- Select the Application Pool used by your site
- Choose advanced settings
- Under Process Model categtory increase the 'Idle Time-out' value to the desired length.

Second, try searching Google for an ASP.NET Keep Alive example. Hope this info helps!