SessionState timeout problem

  • Thread starter Mikko Penkkimäki
  • Start date
M

Mikko Penkkimäki

Hi

Looks like I can not change Web page's timeout setting. In practise it's all
the time 20 minutes - no matter what I do.

I have this kind of setting in web.config:
<sessionState
mode="InProc"
cookieless="true"
timeout="1"
/>

With this settings program goes to Global.asax's Session_End() function
after 1 minute but the session is still running after this. It's only after
20 minutes when the session really stops.

I have tried to change the timeout setting in Machine.config also >> No
difference.
I have even booted my computer after I have made change to the setting -
just in case if something is still running in memory. >> No help.

That 20 minutes settings has to be somewhere hidden, but where? Couldn't
find it from IIS either.

I have Windows XP Pro and Visual Studio .NET 2003.

Please help me.

Regards
Mikko
 
P

Paul Glavich [MVP - ASP.NET]

How are you determining that the session is still running? Is it just that
you dont go back to the login page or something like that?
 
K

Karl

Also, keep in mind that it's 20 minutes from the last activity - ie, it's a
sliding timer not an absolute one.

karl
 
M

Mikko Penkkimäki

Hi

There's no login page in the software. New session is created for every new
user from "HttpContext.Current.Session.SessionID". This SessionID is used
for loading and saving user dependent session data (for
ex."HttpContext.Current.Session["UserDependentVariable_1"]").

I can see that the session is still running because the SessionID is still
the same and all user dependent data is still in session. When I change to
another page in the software after about 20 minutes, the SessionID has been
changed. Session data is also empty - of course.

I have now changed the SessionState's mode to "StateServer". I have read
from the Web that it's not as buggy as "InProc". Still no effect in my
software.

My problem is that there is a need that the session lasts hours - not 20
minutes. I have changed SessionState's timeout to "120" in Web.config and
Machine.config. I also found setting from IIS: Web page Properties >>
Configuration... >> Options: Enable session state, Session timeout. I
changed also this to 120. Still the session is lost after about 20 minutes.

I have tried to find answer to this from the Web. I haven't found any answer
yet but I have found many other programmers who have faced the same problem:
Sessions just don't last long. Is there any way to get over this?

Regards
Mikko
 
J

Jason Bailey

You were in the right place when you poked around in IIS.

Go to the website in question, right-click and choose "Properties".
Click on the "Home Directory" tab
Click on the "Configuration" button
Click on the "App Options" tab on the pop-up window
Choose the session timeout you wish. As you can see on this screen, the
default value built into IIS 5.0 out of the box is 20 minutes.
 
N

naijacoder naijacoder

Hi Jason,
So which one works for Session.Timeout?
The IIS setting or the web config?
Bcos 'm confused!
And which one overrides the other does IIS setting overrides the WEB
CONFIG?
Let me know please.
thanks
 
Joined
Jul 26, 2007
Messages
1
Reaction score
0
Sorry to open up a thread that's a few years old but I'm having the same problem described above with no luck resolving it.
I've changed

sessionstate to 120mins
added machinekey to the web.cofig
iis app pool timeouts to 120mins
sessionstate properties from iismanager-app config

I've done everything I can think of but sessions are still being terminated after about 20 minutes. This doesn't seem to be on a sliding scale either as I can be working on the page for a few minutes and when I go to another page I get kicked back to the 'Default.aspx' screen.

Any suggestions are appreciated
 
Joined
Jun 21, 2009
Messages
1
Reaction score
0
Q: Why does the SessionID remain the same after the Session times out or abandoned?
A:Even though the session state expires after the indicated timeout period, the session ID lasts as long as the browser session. What this implies is that the same session ID can represent multiple sessions over time where the instance of the browser remain the same.

eggheadcafe. com/articles/ 20021016.asp
 
Joined
Jun 7, 2013
Messages
1
Reaction score
0
Hi

Looks like I can not change Web page's timeout setting. In practise it's all
the time 20 minutes - no matter what I do.

I have this kind of setting in web.config:
<sessionState
mode="InProc"
cookieless="true"
timeout="1"
/>

With this settings program goes to Global.asax's Session_End() function
after 1 minute but the session is still running after this. It's only after
20 minutes when the session really stops.

I have tried to change the timeout setting in Machine.config also >> No
difference.
I have even booted my computer after I have made change to the setting -
just in case if something is still running in memory. >> No help.

That 20 minutes settings has to be somewhere hidden, but where? Couldn't
find it from IIS either.

I have Windows XP Pro and Visual Studio .NET 2003.

Please help me.

Regards
Mikko

Great you even booted your computer after you have made change to the setting, great man , but you missed one single thing, you must have reinstalled the windows and that would have surely worked.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

sessionState mode="StateServer" vs. "InProc" 8
Forms timeout, Session timeout 0
sessionState 0
timeout 5
session timeout problem 1
Session Timeout 4
sessionState mode="StateServer" 0
Session Timeout 4

Members online

Forum statistics

Threads
473,787
Messages
2,569,627
Members
45,329
Latest member
InezZ76898

Latest Threads

Top