stuyguy
asked on
Session Timeout Problem After Migrating to .net 3.5
We have migrated a .Net 1.1 applicatoin to .Net 3.5 and are getting very short session timeouts (10 to 20 minutes) even though we have timeout=1000 in the web.config. Any ideas?
Last Comment
lambdabunker
can you post the code where you are setting timeout, can you also post the error/message you get once timeout expires?
ASKER
Here is the line from the web.config:
There is no error message because each page in the application detects if there are certain session variables present. If the session variables are not present the application redirects to the login page. The application is redirecting to the login page after 10 minutes of non-use.
There is no error message because each page in the application detects if there are certain session variables present. If the session variables are not present the application redirects to the login page. The application is redirecting to the login page after 10 minutes of non-use.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks.
ASKER
That appears to have resolved the problem. Thank you.
ASKER
BTW, Any reason not to set the worker process timeout to a very high value. We have a web application with about 30 users a day per web server. We need to keep the session alive for as long as possible.
ASP.NET
The successor to Active Server Pages, ASP.NET websites utilize the .NET framework to produce dynamic, data and content-driven web applications and services. ASP.NET code can be written using any .NET supported language. As of 2009, ASP.NET can also apply the Model-View-Controller (MVC) pattern to web applications
128K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
