A few questions regarding tomcat session replication:

1) is the jvmRoute attribute on Engine object necessary for session replication 
to work correctly?
2) does session replication only work correctly with sticky load balancer 

My setup is
1) load balancer without sticky session routing into kubernetes
2) two pods running tomcat with cloud member provider, which see and find each 

No jvmRoute attribute is set.

Above setup doesn't work and give strange errors for the distributed webapp 
which relies on http sessions.

Should above setup work? If not why and what do I need to fix?

Any hints of what logging to enable to debug the problem if any at all?

To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to