On 04/08/17 20:55, christop...@baus.net wrote: > We are still having an issue with some users losing session information. > I want to use synchronous updates for the DeltaManager. > To enable this should the channelSendOptions be set to 6? That isn't > clear to me from reading the documentation.
Correct. With channelSendOptions 6, the replication message will be sent at the end of the request processing and the request will not complete until the message has been received and processed by the other nodes. Mark > Thanks, > -Chris > > > On Thu, Jul 27, 2017, at 12:37 PM, christop...@baus.net wrote: >>>> Or does the DeltaManager replicate to all nodes? >>> >>> It does, but the issue is one of timing. The main problematic area is>> the >>> user agent being directed to another node before the session data>> has >>> replicated. This can be avoided by configuring sync replication >>> (which slows things down since the response does not complete >>> until the>> replication has completed). >>> >> >> I figured out our issue today. Our servers are multi-honed and the >> multi-cast routing was slightly different on different nodes, so they> >> weren't discovering each other. Explicitly specifying the >> interface to> bind to in the Membership configuration solved the issue. >> >> ---------------------------------------------------------------------> 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
