Last post Feb 26, 2012 12:34 PM by satalaj
Feb 24, 2012 07:11 AM|KunalVishwakarma|LINK
I have a website running on sbs win 2003 server. dedicated in my office. website is developed in .net 2.0 with IIS 6.
When i use 'InProc' state, my users (200-300 dedicated users) are getting ogged off at every 5 minutes (not exatly).
but whien i use 'SQLServer' state, then there is no problem. but website gets slow, and i need to restart sqlservice with sql server agent.
Now I want to use 'InProc' state. how do I do it ?
Feb 24, 2012 07:35 AM|atulthummar|LINK
you can either do it in web.config file Here the timeout "20" is in
minutes if u want u can change in to fit your requirement.
or in the session_start of global.asax
protected void Session_Start(Object sender, EventArgs e)
Session.Timeout = 20;
Feb 24, 2012 09:00 AM|hans_v|LINK
When You use InProc, all Session state is stored in memory. But when the application pool recycles, all session states are lost. So when session is lost at irregular intervals, most likely, your applicatiion pool recycles, so you have to identitfy why that
happens. The next article explains some reasons...
Feb 25, 2012 03:39 PM|roopeshreddy|LINK
Instead of InProc, you can use StateServer mode!
It's a separate ASP.NET State service, which is better than SQL Server!
NOTE: ASP.NET State service should be started!
Hope it helps u...
Feb 26, 2012 12:34 PM|satalaj|LINK
It seems you have configured the IIS to use multiple worker process to server the request. In this case you must store session out of proc.
If you don't want to use SQL session state storage mechanism, you can use Asp.net state server. It's faster as compared to SQL server.
Working with session .
If you want to use InProc sesison mechanism which is default, you need to configure onl one worker process in application pool and you disable load balancing of server. (web farming).