Export to GitHub

memcached-session-manager - issue #223

Session LastAccessedTime it's not updated using MSM No-Sticky Sessions


Posted on Dec 18, 2014 by Quick Giraffe

What steps will reproduce the problem?

  1. Configured multiple Tomcat with two MSM (No Sticky):

    <Manager className="de.javakaffee.web.msm.MemcachedBackupSessionManager"
                memcachedNodes="n2:xxx.xxx.xxx.xxx:11211,n1:xxx.xxx.xxx.xxx:11211"
                sticky="false"
                sessionBackupAsync="false"
                lockingMode="auto"
                requestUriIgnorePattern=".*\.(ico|png|gif|jpg|css|js)$"
                transcoderFactoryClass="de.javakaffee.web.msm.JavaSerializationTranscoderFactory" />
    
  2. Within Web Application JSP

In a JSP that access to http session and calling session.getLastAccessedTime() it always return the same value.

What is the expected output? What do you see instead? Using Tomcat default Session Manager it's updated on every request.

What version of the product are you using? On what operating system?

Environment:

Linux: CentOS release 6.5 (Final) - 2.6.32-431.20.3.el6.x86_64 Apache HTTPD: Server version: Apache/2.2.15 (Unix) JVM: Java(TM) SE Runtime Environment (build 1.6.0_45-b06) - Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode) Apache Tomcat: 7.0.42 Version of MSM: (added all jar in $CATALINA_HOME/lib) * memcached-session-manager-1.8.3.jar * memcached-session-manager-tc7-1.8.3.jar * spymemcached-2.11.1.jar

Additional Information

Sessions doesn't expire and heap memory overflow occurs.

Comment #1

Posted on Aug 24, 2015 by Grumpy Bear

Issues are moved to github, this one is now https://github.com/magro/memcached-session-manager/issues/262. If this is still an issue for you please update the github issue.

Status: New

Labels:
Type-Defect Priority-Medium