Solved

Session variables expiration ASP.NET C#

Posted on 2016-09-23
3
82 Views
Last Modified: 2016-09-23
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
Comment
Question by:Alex E.
3 Comments
 
LVL 12

Expert Comment

by:Ramkisan Jagtap
ID: 41812816
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
 
LVL 75

Accepted Solution

by:
käµfm³d   👽 earned 500 total points
ID: 41813187
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
 

Author Closing Comment

by:Alex E.
ID: 41813261
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

Webinar: Aligning, Automating, Winning

Join Dan Russo, Senior Manager of Operations Intelligence, for an in-depth discussion on how Dealertrack, leading provider of integrated digital solutions for the automotive industry, transformed their DevOps processes to increase collaboration and move with greater velocity.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Wouldn’t it be nice if you could test whether an element is contained in an array by using a Contains method just like the one available on List objects? Wouldn’t it be good if you could write code like this? (CODE) In .NET 3.5, this is possible…
Today I had a very interesting conundrum that had to get solved quickly. Needless to say, it wasn't resolved quickly because when we needed it we were very rushed, but as soon as the conference call was over and I took a step back I saw the correct …
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…

685 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question