| Issue 265: | Web sessions expire before 12 hour timeout | |
| Back to list |
Reported by Shawn Pearce <sop@google.com> on Mon Aug 24 14:51:14 PDT 2009 Source: JIRA GERRIT-266 Affected Version: 2.0.19 I'm seeing my web session timeout much more rapidly than it should. review.source.android.com uses a 12 hour session timeout, which is the default, yet I've seen a session only a few hours old timeout with an invalid xsrfKey error (see GERRIT-265). I think Ehcache is killing cache entries, even though the cache is not yet full, and the timeout has not yet been reached.
Sep 24, 2009
#1
code-rev...@gtempaccount.com
Sep 24, 2009
Comment by Shawn Pearce <sop@google.com> on Wed Sep 02 18:13:44 PDT 2009 This might be fixed by I6e2e67d4e7f0bb2131005627a1e0d446d9990b60, which at least moves to an LRU based store. But it may really turn out to be the case that we can't trust Ehcache with something like this, because I still suspect they are evicting earlier than they should be given the idle timeout we have configured.
Sep 24, 2009
Update by Shawn Pearce <sop@google.com> on Wed Sep 02 18:13:50 PDT 2009 Fixed in version 2.0.21.
Status:
Fixed
Sep 25, 2009
(No comment was entered for this change.)
Labels:
FixedIn-2.0.21
Oct 21, 2012
(No comment was entered for this change.)
Status:
Released
|
|
| ► Sign in to add a comment |