search

bcxs051 / memcached-session-manager

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

Concurrent requests for a non-sticky session on the same tomcat may interfere #111

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Given a setup with non-sticky sessions and lockingMode=none, 2 concurrent 
requests for a session on the same tomcat may interfere:
on the end of the first request the session is removed from the internal 
session map, so that it won't be available at the end of the 2nd request.

Although for non-sticky session with the possibility of concurrent requests for 
the same session a lockingMode != none is strongly recommended, the described 
behaviour might be improved.

Original issue reported on code.google.com by martin.grotzke on 26 Sep 2011 at 10:21

GoogleCodeExporter commented 9 years ago 
I have been working to get memcached-session-manager-1.5.1 functioning properly 
in non-sticky mode and encountered this issue with any lockingMode that I use 
(I have multiple requests for the same session ID hitting my single Tomcat 
instance concurrently).

Original comment by Benjamin...@intuit.com on 22 Nov 2011 at 1:02

GoogleCodeExporter commented 9 years ago 
Fixed. Requests for the same session on the same tomcat are sharing the session 
and can access them concurrently. Only the last request that finishes its work 
will trigger the session storage/backup/update in memcached (which will also 
release the lock if there is any).

Original comment by martin.grotzke on 14 Dec 2011 at 8:44