On 27/06/2020 10:19, Thomas Meyer wrote: > Hi, > > A few questions regarding tomcat session replication:
load-balancing and session replication are two separate parts of an overall clustering solution. > 1) is the jvmRoute attribute on Engine object necessary for session > replication to work correctly? No, but if you don't use it it places a number of restrictions on the web application behaviour and on the configuration of session replication. The limitations are: - you need to use the DeltaManager (which doesn't scale as well as the BackupManager); - any requests made by the client that depend on the session MUST be issued in series, not in parallel; and - the session Manager must be configured to update all the other nodes in the cluster BEFORE the current request returns to the client. > 2) does session replication only work correctly with sticky load balancer > routing? No. It works quite happily without it. > > 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 other > > 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? Please show us how you have configured the session manager and clustering. Mark > Mfg > Thomas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
