This was requested/reported on the mailing list
(http://groups.google.com/group/memcached-session-manager/browse_thread/thread/2
37168484a7b4217):
With a single node configuration (without node id) it's not possible to enable
locking. If tried the following exception is thrown:
2012-01-23T22:49:09+00:00 app[web.2]: WARNING: Could not load session with
id 7A218E2E0D4569248686ADB855FEAE74 from memcached.
2012-01-23T22:49:09+00:00 app[web.2]: Jan 23, 2012 10:49:09 PM
de.javakaffee.web.msm.MemcachedSessionService loadFromMemcached
2012-01-23T22:49:09+00:00 app[web.2]:
java.lang.UnsupportedOperationException: Not supported for single node
configuration without node id.
2012-01-23T22:49:09+00:00 app[web.2]: at
de.javakaffee.web.msm.MemcachedSessionService.findSession(MemcachedSessionServic
e.java:568)
2012-01-23T22:49:09+00:00 app[web.2]: at
de.javakaffee.web.msm.LockingStrategy.acquireLock(LockingStrategy.java:167)
2012-01-23T22:49:09+00:00 app[web.2]: at
de.javakaffee.web.msm.MemcachedSessionService.loadFromMemcached(MemcachedSession
Service.java:998)
2012-01-23T22:49:09+00:00 app[web.2]: at
de.javakaffee.web.msm.LockingStrategy.lock(LockingStrategy.java:134)
2012-01-23T22:49:09+00:00 app[web.2]: at
de.javakaffee.web.msm.LockingStrategyAuto.onBeforeLoadFromMemcached(LockingStrat
egyAuto.java:133)
Original issue reported on code.google.com by martin.grotzke on 25 Jan 2012 at 8:30
Original issue reported on code.google.com by
martin.grotzke
on 25 Jan 2012 at 8:30