Hey, > If you do not set the LocalMember, > the implementation class of local members will become MemberImpl rather than > the StaticMember. > In addition, you can not explicitly specify the domain and the uniqueId of > local member. > If you do not mind these, there is no problem if you do not set LocalMember.
According to the configuration example, it is possible to set the uniqueid/domain. Could you clarify your statement? https://tomcat.apache.org/tomcat-7.0-doc/config/cluster-interceptor.html <Interceptor className="org.apache.catalina.tribes.group.interceptors.StaticMembershipInterceptor"> <LocalMember className="org.apache.catalina.tribes.membership.StaticMember" port="4000" securePort="-1" host="tomcat01.mydomain.com" domain="staging-cluster" uniqueId="{1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,1}"/> <Member className="org.apache.catalina.tribes.membership.StaticMember" port="5678" securePort="-1" host="tomcat01.mydomain.com" domain="staging-cluster" uniqueId="{0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15}"/> </Interceptor> > The heartbeat is chained. > Container->Cluster->channel->Interceptor(TcpPingInterceptor)->ChannelSender > When using a static membership, TcpPingInterceptor does the nodes failure > detection. > Therefore, when using a static membership, TcpPingInterceptor is required. I understand the concept of this chain, but I want to understand WHY there are these 3 points to enable the heartbeat instead of a central one? I don’t see a reason to send the heartbeat on different levels of the chain. Regards Hajo --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
