Strange timeout in Sitecore 7

Question

I have been using Sitecore version 7.1 for several months and noticed that the Sitecore client registers me after a downtime of about 20 minutes. Other users have reported these issues when editing content.

I am using Windows 7, IIS 7, .NET framework 4.5.

I checked the error log for anything and I see no obvious errors and the keepalive service is working - I get this information in the logs:

ManagedPoolThread #14 12:47:24 INFO Scheduling.UrlAgent started. Url:http://testsite/sitecore/service/keepalive.aspx 

I get some of them in a magazine, but can this be related?

 WARN Memory usage exceeded the MemoryMonitor threshold 

When I get back to the site, leaving it for 20 minutes. I take these log entries.

 952 15:08:28 INFO AUDIT (sitecore\grahams): Logout 952 15:08:28 WARN Protected page accessed with no current user 6440 15:08:28 INFO AUDIT (sitecore\grahams): Logout 6440 15:08:28 WARN Protected page accessed with no current user 

Any body seen this case before or having any clues on how I could get to the bottom of this?

Thank you in advance

Yang

Answer 1

We also experience the same or similar problems as we upgrade several of our websites to Sitecore 7.1. We continue to explore all the settings mentioned above, but have not yet found an explanation.

This may help, depending on your situation . Sitecore confirmed that a new problem was introduced: when several users logged in with the same credentials, and one of them logged out, all the others also logged out automatically.

They released a temporary hotfix package specifically designed for version 7.1 rev. 140130. Before installing, make sure your solution is updated to version:

https://dl.sitecore.net/hotfix/Sitecore%20CMS%207.1%20rev.%20140130%20Hotfix%20405020-2.zip

Use the package installation wizard to apply the hotfix. We hope that this will be included in the next service pack 7.1.

UPDATE

I continue to discuss with sitecore support on this issue, and although they did not give me a specific fix or fix, there seems to be a way to increase the timeout. This is not without side effects, but it is at least an option at the moment. I am testing this myself, but now I will share and update everyone according to my progress.

Change or add the following three parameters to your web.config (in the example below 2 hours):

Client Timeout

 <setting name="Authentication.ClientSessionTimeout" value="120" /> 

Form Timeout

 <authentication mode="None"> <forms name=".ASPXAUTH" cookieless="UseCookies" timeout="120" /> </authentication> 

Session Timeout

 <sessionState mode="InProc" ... timeout="120" /> 

Answer 2

There are several configurations required for verification.

Sitecore has a client timeout setting:

 <setting name="Authentication.ClientSessionTimeout" value="60"/> 

Make sure it is not set for 20 minutes.

Next you should check your session timeout here:

 <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"/> 

Answer 3

I survived that this is a problem with Sitecore 8.2 rev 170728 (Update 5). In my case, the cause of the problem was that I accessed the site via HTTP, while the following parameter in the web.config file did not allow:

 <httpCookies httpOnlyCookies="true" requireSSL="true" /> 

The problem can be fixed either by providing access to the site via HTTPS, or by setting the attribute "requireSSL" to "false" in the above setting.