Closed GoogleCodeExporter closed 9 years ago
Is memcached on server1 running?
Original comment by martin.grotzke
on 8 Mar 2010 at 4:06
What I could reproduce: When both memcacheds are not available then with every
request a
new session was created and the session id sent as a cookie.
This is fixed now: When generating a session id, only valid memcached node ids
are encoded.
If there's no memcached available, the session id will not contain a memcached
id. Also
when a session, that was previously stored in memcached, cannot be stored as no
memcacheds
are available, this will not trigger a new session.
This change is implemented in the develop branch and will be release with 1.2
(probably
next week). If you want to test this earlier I could provide a packaged jar.
Original comment by martin.grotzke
on 8 Mar 2010 at 11:56
Original issue reported on code.google.com by
mdie...@gmail.com
on 23 Feb 2010 at 9:19