deeplyloving / memcached-session-manager

Automatically exported from code.google.com/p/memcached-session-manager
0 stars 0 forks source link

Tomcat is creating a new session id on every request. #211

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Hello,

 Tomcat is creating a new session id on every request.

Example:

When I access the url http://localhost/backend three times 3 ids were generated 
in each of the requests and I can never login because of the captcha code.

What am i doing wrong?

Versions:
apache-tomcat-7.0.50
memcached-session-manager-1.8.2.jar
memcached-session-manager-tc7-1.8.2.jar
spymemcached-2.11.1.jar

<Manager className="de.javakaffee.web.msm.MemcachedBackupSessionManager"
         memcachedNodes="n1:localhost:11211"
         sticky="false"
         lockingMode="none"
     sessionBackupAsync="false"
         sessionBackupTimeout="1000"
     requestUriIgnorePattern=".*\.(ico|png|gif|jpg|css|js)$"/>

Original issue reported on code.google.com by r.pr...@gmail.com on 13 Aug 2014 at 4:42

GoogleCodeExporter commented 9 years ago
Please configure debug logging according to the docs and provide the related 
log output. 

Original comment by martin.grotzke on 13 Aug 2014 at 5:28

GoogleCodeExporter commented 9 years ago

Original comment by r.pr...@gmail.com on 13 Aug 2014 at 6:03

Attachments:

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Hi Martin,

  I found another problem that may be related to the above. I'll try to explain the scenario:

I have 1 tomcat using memcached with 2 applications (two .war)

First Application

backend.war
Context Path: "/backend"
Url: http://localhost:8080/backend

Second Application

ROOT.war
Context Path: "/"
Url: http://localhost:8080/

When I access the second url, tomcat/memcached generated a new session with id 
471CC32D5AF17E703F43408A03EBEA56-n1 . Its works without any problem. When I try 
to access the url http://localhost:8080/backend/login the server receive 
the same session id 471CC32D5AF17E703F43408A03EBEA56-n1, then the admin 
application will generate a new session id on each request. The ids are 
conflicting between the two applications.

How can i use memcached with an application using context path "/"?

Thank You

Original comment by r.pr...@gmail.com on 15 Aug 2014 at 2:03

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

Original comment by martin.grotzke on 24 Aug 2015 at 3:18