Closed GoogleCodeExporter closed 8 years ago
You should be able to use a session-timeout of 43200 (30 days, see
https://github.com/memcached/memcached/blob/master/doc/protocol.txt#L79). Is
that an acceptable workaround for you?
Original comment by martin.grotzke
on 18 Dec 2013 at 9:54
Original comment by martin.grotzke
on 18 Dec 2013 at 10:46
Btw, I saw that for non-sticky sessions msm passes 2 * sessionTimeout to
memcached, so right now (in 1.6.5) the max sessionTimeout for non-sticky
sessions should be 21600.
Original comment by martin.grotzke
on 19 Dec 2013 at 10:04
In response to your question, the workaround is fine. I was just trying to be
a good samaritan and file the bug. I couldn't find any documentation or an FAQ
on the issue, but a couple people did complain about it with no resolution, so
I wanted to make sure the bug was filed. The issue was driving me absolutely
crazy for a while so I am just glad I figured how to work around it.
I know about the memcached 30 day expiration "feature" but for some reason I
could not get it to break with 43200. Either way, I am good.
thanks!
Original comment by scott...@gmail.com
on 28 Dec 2013 at 1:22
Yeah, thanx for filing the issue. It's fixed in 1.7.0 I released some days ago.
Cheers
Original comment by martin.grotzke
on 28 Dec 2013 at 6:48
Original issue reported on code.google.com by
scott...@gmail.com
on 12 Dec 2013 at 6:54