[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 240
  • Last Modified:

Session variables expiration ASP.NET C#

We have an application that uses session variables in this form:

Session["FirstName"] = "test";

Open in new window


And we collect like this in other pages:

result = Convert.ToString(Session["FirstName"] );

Open in new window


We are using one Application Pool configured with NET 4, Enable 32 bits apps,  queue length 1000, Identity:ApplicationPoolIdentity and Idle timed out we changed from 20 to 1000.

We changed the idle time from 20 to 1000 because we noted in event viewer we found this warning:"A worker process with process id of '18404' serving application pool 'webapplication' was shutdown due to inactivity.  Application Pool timeout configuration was set to 20 minutes.  A new worker process will be started when needed."

After change the 20 to 1000 the warning is no more in the event viewer like if was solved the issue of our main problem. This is our main problem:

Now the real reason we changed from 20 to 1000 in idle time is because if we  have opened the browser and inactive for some time the application then the session variables loss their values. Then the change from 20 to 1000 not work at all because the session variables continue losing their values.

How can we solve the session variables loss their values?
0
Alex E.
Asked:
Alex E.
1 Solution
 
Ramkisan JagtapLead DeveloperCommented:
1. set sessiontimeout in web.config.
2. Set session timeout to 60 minutes in IIS manager/Web site properties/ASP.NET configuration settings.
3. Set idle timeout to 60 minutes in application pool properties/performance.
0
 
käµfm³d 👽Commented:
The application pool effectively is the instance of your application in memory. If you are using in-memory session (which is the default), then once your app pool is shut down, session is gone. This is the same thing that would happen if your web application were a console application and you closed the console window while the app was running. If you want to persist the session across application restarts, then you will to move away from in-memory session to something like storing session in a database or some other session provider.
0
 
Alex E.Author Commented:
Exactly I tried everything including change all asp.net timeouts and nothing. I switched to  "Stateserver" and problem gone. Here is what I used:

<sessionState mode="StateServer" stateConnectionString="tcpip=localhost:42424" stateNetworkTimeout="56000" timeout="56000">
    </sessionState>
0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now