Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tomcat session does not persist for multiple tomcat pods with the Memcached session manager #462

Open
amitanwar opened this issue Jan 2, 2024 · 2 comments

Comments

@amitanwar
Copy link

Hello,

There are multiple pods for Tomcat, and for session management, we use Couchbase with the Memcached session manager

Pods
tomcat-0
tomcat-1
tomcat-2

"Ideally, we expect the behavior to be as follows: If I initiate the request using http://localhost:8089/ and the session is initiated by 'tomcat-0' with the session ID 'AB312C4BBD371551735C4950858E98A7.dev,' it should be considered valid for 'tomcat-1' and 'tomcat-2.' However, it is not working as expected; if the session is created by 'tomcat-0,' it is valid only for 'tomcat-0' and not for the other pods."

What am I doing wrong?
Versions: apache-tomcat-8.0.50 memcached-session-manager-1.9.5.jar memcached-session-manager-tc7-1.9.5.jar spymemcached-2.11.1.jar

<Manager className="de.javakaffee.web.msm.MemcachedBackupSessionManager"  memcachedNodes="n1:localhost:11211" 
 memcachedProtocol="binary"  username="xyz"  password="xyz" />
@LLY-SC
Copy link

LLY-SC commented Jan 2, 2024 via email

@amitanwar
Copy link
Author

Can someone review the problem statement?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants