In my application i am facing session timeout issue . What happens is that suddenly users kicked out . I surf alot for solution and did many things . Like increasing session timeout , idle timeout ,implemented keepalive . But issue still exists
Is it possible that its due to internet connectivity . Because i saw multiple time in console that net::Error connection-reset , Network-changed etc etc.
If yes then what could be the possible solution for this .
Thanks,
Session timeout is controlled by the following key in web.config...
<system.web>
<sessionState mode="InProc" timeout="30" />
</system.web>
Related
In a project (build with Sitecore version 6.6 and ASP.net Webforms) I experience a strange session loss issue on Content Delivery (CD) server. I googled on this subject using the keywords ASP.net and session loss. I found a lot of interesting stuff, but not the solution.
In the meanwhile, I figured out that it is nearly impossible that the cause of the issue is an Application Pool recycle or the auto-bot detect function inside Sitecore.
The way we write data to the session.
System.Web.HttpContext.Current.Session["name"] = "data here";
The way we read data from a session.
string data = (string)System.Web.HttpContext.Current.Session["name"];
SessionState configuration
<sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;user id=sa;password=" cookieless="false" timeout="20" />
The Sitecore configuration is the default. The session loss is at random times within 5 minutes. Does anyone know a solution?
One possible reason is following setting.
<authentication mode="None">
<forms name=".ASPXAUTH" cookieless="UseCookies" timeout="180" />
</authentication>
Also look at session setting in IIS, probably there is something incorrectly setup.
I would suggest that you try setting up a session state server and see if the problem still persists.
Additionally, it is worth to ask, are you using one or multiple CD servers.
I have a ASP.Net web application in witch i want to put a timeOut (for user that dosen't do anything for too much time). My test use a 3 secondes timeOut. In the web.config :
<sessionState mode="StateServer" stateNetworkTimeout="3"></sessionState>
I get the following error as soon as i run my app:
Cannot request session state in session state server.
I can't find anything relevante for this case...
i tried to put InProc in Mode="" but it dosen't timeout anything.
Looking at this, you're trying to use a State Server and set the idle time between the web server and the state server. To properly configure the web server to use a state server, you must also configure the state server. Go to your state server and run:
systemroot\Microsoft.NET\Framework\versionNumber\aspnet_state.exe
This will install the asp.net state service. Then in the sessionState element in your web config you will need to set the stateConnectionString attibute as well.
<configuration>
<system.web>
<sessionState mode="StateServer"
stateConnectionString="tcpip=SampleStateServer:42424"
cookieless="false"
timeout="20"
stateNetworkTimeout="3"/>
</system.web>
</configuration>
You now have two "timeouts" here. The "timeout" attribute is how long the user can keep a connection to the webserver. The stateNetworkTimeout is how long the webserver to stateserver connection can be idle. The default is 10 seconds.
Hope this helps.
ref: https://msdn.microsoft.com/en-us/library/ms178586(v=vs.100).aspx
/ip
<sessionState mode="InProc" timeout="1" cookieless="false" ></sessionState>
I mistaken secondes for minutes, the Timeout value is about minutes. So i waited 1 minute for my test...
Thanks to #Devian and #Agolo.
I am facing session expiring issue in my ASP.NET Web Forms application. The session is timing out randomly. After 5 to 10 minutes(not exact time but happening randomly) there is no any explicit session. Timeout declaration elsewhere in the code. Given below are settings I have defined in Web.Config file. Any help is much appreciated
<httpRuntime maxRequestLength="350000" enableVersionHeader="false"
maxQueryStringLength="3584" executionTimeout="180000"/>
<sessionState mode="InProc" timeout="30"></sessionState>
I have an ASP site where the session would expire within 30 minutes or sometimes less. The Session mode was 'InProc', so I changed it to 'StateServer', and also started the 'ASP.NET State Service', but I am still running into similar issues. I also changed the application pool's 'Idle Time-out' to '0'.
<sessionState cookieless="false" mode="StateServer" stateConnectionString="tcpip=localhost:42424" stateNetworkTimeout="20" />
Any idea why the session is expiring or not sticking around after leaving the application idle for about 30 minutes or less?
Thanks.
Sanjeev
There is a session timeout you can set, it takes number of minutes.
<sessionState ... timeout="60" />
I have an intranet page which needs to not time out (indefinitely) and I'm using JS to keep it alive that way.
But I am having one issue that happens when the user loses the connection (happens frequently due to to going in and out of wifi range) the session times out then.
How can I keep the session up/refresh it if that happens?
How about increase the session time out on web.config ?
<configuration>
<system.web>
<sessionState timeout="120"></sessionState>
</system.web>
</configuration>
http://msdn.microsoft.com/en-us/library/system.web.sessionstate.httpsessionstate.timeout.aspx
Other possible way is to make your database, connected with the user cookie, and use your "custom session" data that are totally connected with your users.
Try using in web config if you are using Form Authentication
<system.web>
<authentication mode="Forms">
<forms timeout="120"/>
</authentication>
<sessionState timeout="120" />
</system.web>
first Sets the session timeout on the server is for all session
Rather than a single Session
out wifi range is the entire network are broken
so not keep alive
You have to use cookie
use cookie keep alive