Last post Feb 01, 2018 09:04 AM by AngelinaJolie
Jan 31, 2018 03:10 PM|Fredy511|LINK
Jan 31, 2018 04:27 PM|bruce (sqlwork.com)|LINK
publishing an app will force are recycle, which when using inproc session, will kill all sessions.
Feb 01, 2018 09:04 AM|AngelinaJolie|LINK
p , some times it work fine and other times we recieve the message Your session has expire,
Sir, there are many possible causes for this problem.
This problem can occur when antivirus software scans the Web application files. During the scanning process, the antivirus software may mark the Global.asax, the Web.config, and/or the Machine.config files as modified. This modification
prompts the Microsoft .NET Framework restart the Web application. If the session data is stored in-process, all session data is lost whenever a Web application is restarted. From PRB:
Session variables are lost intermittently in ASP.NET applications
So why not use mode="StateServer", it will fix your problem.
<sessionState mode="StateServer" stateConnectionString="tcpip=127.0.0.1:42424" cookieless="false" timeout="1800"/>
note : stateConnectionString="tcpip=127.0.0.1:42424" is default,so we could remove it ;
and it uses StateService to store Session, and Session will not be lost unless the computer is restarted or the StateService is broken.
Because Session information is stored in other processes, not in IIS so that the loss of Session information caused
by the collapse or reboot of the IIS process is avoided. But this way requires that information stored in Session must be serialized, and then be serialized when it is acquired from Session, which results in a slight loss of performance.
To use StateServer mode, make sure the ASP.NET state service is running on the server used for the session store. The ASP.NET state service is installed as a service when ASP.NET and the .NET Framework are installed. The ASP.Net state
service is installed at the following location:
With regards, Angelina Jolie