Session Timeout in IIS 7

Question

I like to host the asp.net web application in IIS 7.0 (Windows Server 2008).

I configured the session state as sessionstate mode = "inproc" timeout = 120. Even the session expires after 15 seconds. What could be the problem?.

thanks

Answer 1

Check the Windows event log to ensure that the workflow will not be re-created.

There might be something in your code that forces Worker Process to force recyle, in which case when the session is stored inProc, it will lose all the session values ​​that it holds.

Answer 2

You can check connection timeouts in these two areas.

OR

Answer 3

it sounds like the session timeout is set incorrectly in the web.config file, you can try something like:

<system.web> <sessionState timeout="2" /> 

to set a timeout of 2 minutes

http://msdn.microsoft.com/en-us/library/h6bb9cz9(vs.71).aspx

Answer 4

Mmerrell wrote this and is the key to finding the origin of the problem:

Check the Windows event log to make sure that the workflow is not being forced to redo.

There might be something in your code that forces the Worker Process to force itself to process, and in this case, when the session is stored inProc, it will lose all the session values ​​that it holds.

Look at the event viewer in the "Windows Logs / System", you are looking for the source event "WAS", which contains a description of the type: "Workflow with process identifier" 2980 "serving the application pool" SIAC "was disabled due to inactivity. The application pool timeout configuration was set to 20 minutes. A new workflow will be launched if necessary. " this is the symptom you are looking for.

View events with a WAS event

Hope this helps.

Answer 5

Had pretty much the same problem with an HTTP handler written in C # using SessionState. It seems the IsReusable property should be false, otherwise I worked in a session problem.

Thanks to Mmerrell for his answer that led me on the right track.

Answer 6

There is one more thing that needs to be checked - additional settings for the Pool Pool application - virtual memory limitation. See if it is explicitly set - since it can be automatically recycled, it once exceeds the set limit. Especially if you see an error in the event log, for example:

A workflow with process identifier "****" serving the application pool "your-app-pool-name" requested processing because it reached the limit of its virtual memory.