search

bossadvisors / memcached-session-manager

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

Memcached node failover does not work for non-sticky sessions #83

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Install 1 Tomcat 7.0.8
2. Configure 2 Memcached Nodes
3. Visit some pages and remove 1 node

What is the expected output? What do you see instead?
Pages can not be accessed anymore - Connection refused exceptions

What version of the product are you using? On what operating system?
session-manager-tc7-1.4.0-RC3.jar (attached is a config snippet)
Tomcat 7 on Windows 7 64 bit, Memcached nodes on Ubuntu 10.0.4

Please provide any additional information below.
Another question:
Does the normal cluster replication (BackupManager) working together with this 
manager? Will the normal BackupManager then also check session modification?
It would be perfect if the normal BackupManger would work also if no memcached 
node is available.

Original issue reported on code.google.com by Zoi...@gmail.com on 15 Feb 2011 at 2:45

Attachments:

GoogleCodeExporter commented 9 years ago 
Fixed now.

Actually it was not an issue with tomcat7 but with non-sticky sessions. For 
non-sticky sessions the session is stored additionally in a secondary memcached 
node. If this node was not available the related exception made its way up to 
the container so that the request failed. Fixed for tomcat6 and tomcat7, see 
the attached jars.

Original comment by martin.grotzke on 15 Feb 2011 at 10:41

Attachments:

GoogleCodeExporter commented 9 years ago 
Btw, to get notified on updates/releases you should join the mailing list

Original comment by martin.grotzke on 15 Feb 2011 at 10:52