>> IIS 6.0 (and probably 7) has a setting that controls
As our message stated, "I have a Windows 2000 Server (SP4)... within IIS 5"
What v 6 and 7 have is of little help.
>> let's say you have the Idle timeout set to 10 minutes to save resources.
The lost session state is taking place within a span of 30 SECONDS! It only takes me 10 seconds to input bogus data on profile1.aspx and click the NEXT button, taking me (or, SHOULD be taking me) to profile2.aspx. However, instead of forwarding me to profile2.aspx (the next page), the app throws the user to the login.aspx page, because the user session has already been lost.
Main Topics
Browse All Topics





by: wolfman007Posted on 2009-01-23 at 02:40:18ID: 23447754
StateServer stores session state in a separate process, so the state is preserved if the application is restarted.
com/2008/0 7/aspnet-s ession- tim eouts.html
You might have been losing sessions between pages if the app pools settings were causing it to be recycled because IIS thought the app pool was idle.
Idle Timeout
IIS 6.0 (and probably 7) has a setting that controls how idle processes are handled.
This can also affect the session timeout indirectly. This is the case when let's say you have the Idle timeout set to 10 minutes to save resources. If your site is not used a lot and say that the only user using your site stopped using it 10 minutes ago, this means that your application will get recycled. One of the side effects of an application getting recycled is that all sessions are terminated also. So, in this case even if your session is set to timeout say in 30 minutes, under some conditions (little traffic), it is effectively 10 minutes.
http://justgeeks.blogspot.