Many thanks Mark!
-Original Message-
From: Mark Thomas
Sent: 01 February 2022 09:25
To: users@tomcat.apache.org
Subject: Re: Tomcat 9 Session replication
On 31/01/2022 14:54, Alan F wrote:
> Many thanks Chris,
>
> Don't laugh I was looking at those values after Keiic
Schultz
Sent: 31 January 2022 14:46
To: users@tomcat.apache.org
Subject: Re: Tomcat 9 Session replication
All,
On 1/31/22 08:04, Keiichi Fujino wrote:
If you use StaticMembershipService, you must set
Cluster#channelStartOptions to 15 (default).
To spell that out (since the docs aren't very explicit
bers. Just make sure you have your ports
unique for each cluster and your membership ids unique for each node in
each cluster.
-chris
-Original Message-
From: Christopher Schultz
Sent: 31 January 2022 14:46
To: users@tomcat.apache.org
Subject: Re: Tomcat 9 Session replication
All,
On
interference ie specifying group or unique id etc.
-Original Message-
From: Christopher Schultz
Sent: 31 January 2022 14:46
To: users@tomcat.apache.org
Subject: Re: Tomcat 9 Session replication
All,
On 1/31/22 08:04, Keiichi Fujino wrote:
> If you use StaticMembershipService, you must
>
>
>
>filter=""/>
>className="org.apache.catalina.ha.session.JvmRouteBinderValve"/>
>
>className="org.apache.catalina.ha.deploy.FarmWarDeployer"
> tempDir="/opt/tomcat/war-temp
@tomcat.apache.org
Subject: Re: Tomcat 9 Session replication
On 28/01/2022 17:05, Alan F wrote:
> We are currently getting traffic from all cluster members in other
> environments using .staticmember opposed to multicast can I confirm why this
> is see below.
>
> What do we need to set here
On 28/01/2022 17:05, Alan F wrote:
We are currently getting traffic from all cluster members in other environments
using .staticmember opposed to multicast can I confirm why this is see below.
What do we need to set here for a clustered pair to make them unique and talk
to eachother only
