2

I have the following config in an attempt to allow the session to be retained for around 239 minutes, however the session is lost in less than an hour.

<system.web>
<sessionState mode="InProc" timeout="240" />
<compilation debug="true" targetFramework="4.0">
  <assemblies>
       ...
  </assemblies>
</compilation>
<authentication mode="Forms">
  <forms loginUrl="~/Account/LogOn" timeout="239" />
</authentication>
<pages>
  <namespaces>
       ...
  </namespaces>
</pages>

I don't believe there to be any C# code overriding these settings.

Does anyone know why this might be happening?

tereško
  • 58,060
  • 25
  • 98
  • 150
user30803
  • 845
  • 2
  • 11
  • 25
  • When you use InProc on the session, is very possible to lose it earlier. Try to move it to the database. – Aristos Mar 07 '13 at 12:54

2 Answers2

3

you also have an idle time-out setting on the application pool process which is set to 20 minutes by default, e.g. every 20 minutes (if no activity) the app pool is reset which also would throw away any active in-proc sessions.

enter image description here

Rickard
  • 2,325
  • 13
  • 22
0

The way that session timeouts and forms authentication timeouts work completely different.

Community
  • 1
  • 1
Can Guney Aksakalli
  • 1,320
  • 1
  • 11
  • 24