Martin Grotzke

Hi Greg, I'm currently on vacation and writing from my phone... With one user in dev you definitely should try to understand what's causing the warning. Please search the mailing...

A lock for one session cannot (_should not_) affect obtaining a lock for another session, as it's based on the sessionId. You might want to review the related code: https://github.com/magro/memcached-session-manager/blob/master/core/src/main/java/de/javakaffee/web/msm/LockingStrategyAuto.java#L117

Is the session timeout / maxInactiveInterval defined in server.xml/context.xml? This one would be preferred over web.xml.

In fact msm should delete the cookie via an appropriate Set-Cookie header. It should also delete the session from memcached. Please activate debug logging (https://github.com/magro/memcached-session-manager/wiki/SetupAndConfiguration#configure-logging) and share the related logs....

Thanks for reporting this! Do you want to submit a PR?

You're right, as documented failoverNodes cannot be used if couchbase uris like http://host1.yourdomain.com:8091/pools are configured in memcachedNodes (which are kind of seed nodes IIRC, from which the couchbase client retrieves...

Awesome, sounds great! :-)

Sounds great to be able to use msm with tomcat-maven-plugin, so thanx a lot for the PR already! The changes basically look good, I've already added comments to the commit....

> The properties I selected came from TomcatBuilder.java in the core project. In fact, with a bit of abstraction and interfacing, I guess you could change TomcatBuilder to use this...

> I'm not sure what you mean by digester, but I do agree centralizing the > configuration properties would be a great idea. With digester I'm referring to http://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/tomcat/util/digester/package-summary.html#package_description. But...