Sandeep Prajapati's Blog

Getting Started with Adobe After Effects - Part 6: Motion Blur


	Blogs

Upload Image

Close it

Select File


	Like

Invite Friends

Browse by Tags · View All

.NET	1
ASP.Net	1
#ASP.Net	1
#DOTNET	1
Deployment	1
Application Pool	1
IIS 7	1

Archive · View All

December 2011

Home · Posts · Most Liked · Most Discussed · Ask a Question · Fans (42) · Preferences

Session Timeout in IIS 7 - Worker Process of ApplicationPool

Dec 21 2011 4:15AM by Sandeep Prajapati

Problem
Recently while testing my application, I was facing problem of Session time out.
By Default Session time is 20 mins and I wanted to extend it

Attempts
if we want to extend it we can set in web.config within System.web tag
<sessionState mode="InProc" timeout="30"></sessionState>
that I already have done.
I set it as 30 mins.
but still my session was getting timed out after 20 min.
So I doubt that it doesn’t apply to my Code so I set It by code also like

System.Web.HttpContext.Current.Session.Timeout = 30;

still no progress

Resolutions
after a long invastigation I came to know Its because Of Default Settings of ApplicationPool for the application in IIS.

There is a setting for Worker process of IIS which will set memory and resource to allot to application application wide.

in my case I was testing my application alone. So application was being idle for more than 20 min to check weather session is alive or not..

To open the settings refer the steps

Type “inetmgr” in run window to open IIS
from left pane “Connections” select your application.
right click on your application and refer the image to open “Advanced Settings” of application(to check which ApplicationPool is referred by application )

from “Application Settings” window you can see the Name of ApplicationPool. like Asp.net V4.0, DefaultAppPool, Asp.net V4.0 Classic.
now close both opened windows.
from left pan double click on “Application Pools”, a list of created application pools will be displayed. if you want to create new application pool for specific application refer this
Right click on the ApplicationPool that was assigned to your Application and click on "Advanced Settings...."

in the popup window ... check the Idle time out for ... that cause the timeout while web application is idle.

Here are the steps to set Idle time..

Happy Deploying...

Tags: IIS 7, Application Pool, Deployment, #DOTNET, #ASP.Net, ASP.Net, .NET,

Previous:
Next:

Sandeep Prajapati

60 · 3% · 926

Liked

Lifesaver

Refreshed

Learned

Incorrect


Like this
Post this to my facebook wall
Tweet this
This was a true life saver
Thanks, this helped me to refresh my memory
Very informative, I just learned something new
I disagree, this information is incorrect


	Submit

4 Comments

Thanks sandeep....

Not aware of this before..I thought session timeout will be controlled by web.config setting..

What is the approach we need to follow, if 2 websites sharing same application pool and if they wants to maintain their own session timeout??

commented on Dec 22 2011 10:26PM

Ramireddy

2 · 41% · 12972

In that case, you have to create different ApplicationPools.. Basically , this timeout will happen only if Web Application is idle on server

commented on Dec 23 2011 3:50AM

Sandeep Prajapati

60 · 3% · 926

Another option is that you can basically disable the app pool idle timeout by setting the time to 0. I've seen this recommended by a few different people from Microsoft for sites that don't have heavy usage. This would also cause your web.config session timeout values to be used, rather then having the app pool clear out and end your sessions.

I also believe the reason you were running into idle time-out issues is because no one was accessing your site for 20 minutes, including the user who was sitting idle. If your session timeout is 30 minutes and the user has sat idle for 25 minutes and no one else has accessed the site, the idle timeout on the app pool would have kicked in and caused your session variable to be cleared out. If your site has moderately high traffic this shouldn't become an issue, but if you have a low traffic site or your site has slow times then the idle timeout value could become an issue.

commented on Jan 13 2012 2:21AM

ajrawson

2893 · 0% · 2

Yes ajrawson Exactly...

Thanks.. And generally for web applications running on some corporate or Fixed hour job locations... My scenario was one of them..

Thanks for understanding and comment :)

commented on Jan 13 2012 12:32PM

Sandeep Prajapati

60 · 3% · 926

Your Comment

Sign Up or Login to post a comment.

"Session Timeout in IIS 7 - Worker Process of ApplicationPool" rated 5 out of 5 by 1 readers