As I understand that LocalMember - is my local node, and Member - is another 
node in the cluster and uniqueId's must be different?

--------------------------------------------
Вт, 2.8.16, Keiichi Fujino <kfuj...@apache.org> пишет:

 Тема: Re: Problem with Cluster after upgrade to Tomcat 8.0.36.
 Кому: "Tomcat Users List" <users@tomcat.apache.org>
 Дата: Вторник, 2 август 2016, 17:03
 
 2016-08-01 22:48
 GMT+09:00 false <unicode_i...@yahoo.com.invalid>:
 
 > Hi all.
 >
 > Tomcat-8.0.36; JDK
 1.8.0_102; CentOS 6.8. After upgrade from 8.0.28 to
 > 8.0.36 I have problem with my cluster. I
 use static membership cluster with
 > two
 nodes with BackupManager. After update I have errors in
 default.log:
 > "WARN 
 org.apache.catalina.tribes.tipis.AbstractReplicatedMap -
 Notified
 > member is not registered in
 the membership", but all works fine (packets
 > exchanging between two nodes on tcp/4000).
 This message gone only if set
 > default
 channelStartOptions (enable multicast), but not
 > channelStartOptions="3". I try
 to downgrade version of Tomcat and this
 >
 problem are not present in tomcat < 8.0.30.
 >
 > My config works a few
 years w/out problems.
 >
 > server.xml:
 >
 > ...
 > <Cluster
 className="org.apache.catalina.ha.tcp.SimpleTcpCluster"
 >                         
 channelSendOptions="8"
 >   
                      
 channelStartOptions="3">
 >
 >             
        <Manager
 >
 className="org.apache.catalina.ha.session.BackupManager"
 >                           
   expireSessionsOnShutdown="false"
 >                           
   notifyListenersOnReplication="true"
 >                           
   mapSendOptions="6"/>
 >
 ...
 >
 > <Sender
 >
 className="org.apache.catalina.tribes.transport.ReplicationTransmitter">
 >                         
    <Transport
 >
 className="org.apache.catalina.tribes.transport.nio.PooledParallelSender"
 >                           
             timeout="5000"/>
 >                     
    </Sender>
 >     
                    <Interceptor
 >
 className="org.apache.catalina.tribes.group.interceptors.TcpPingInterceptor"/>
 >                     
    <Interceptor
 >
 className="org.apache.catalina.tribes.group.interceptors.TcpFailureDetector"/>
 >                     
    <Interceptor
 >
 >
 
className="org.apache.catalina.tribes.group.interceptors.MessageDispatch15Interceptor"/>
 >
 >             
            <Interceptor
 >
 >
 
className="org.apache.catalina.tribes.group.interceptors.StaticMembershipInterceptor">
 >                         
    <Member
 >
 className="org.apache.catalina.tribes.membership.StaticMember"
 >                           
          port="4000"
 >                           
          securePort="-1"
 >                           
      
    host="${catalina.cluster.member.host}"
 >                           
          domain="staging-cluster"
 >                           
          uniqueId="{${
 >
 catalina.cluster.member.unique.id}}"
 >                           
      />
 >           
              </Interceptor>
 >
 >
 Hi.
 
 You can
 define the <LocalMember> in order to avoid this
 warning log.
  -
 
http://tomcat.apache.org/tomcat-8.0-doc/config/cluster-interceptor.html#Static_Membership
  -
 
http://tomcat.apache.org/tomcat-8.0-doc/config/cluster-interceptor.html#Nested_Components
 
 In more detail,
 This is the side effects caused by r1716305 and
 r1716327.
 Actually, this warning log does
 not result in much of a problem because the
 replicationMap can build the appropriate
 membership by the ping mesage.
 I've
 already fixed this problem at r1720074.
 
 
 
 >
 ---------------------------------------------------------------------
 > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 > For additional commands, e-mail: users-h...@tomcat.apache.org
 >
 > --
 > Keiichi.Fujino
 > <users-h...@tomcat.apache.org>
 
 <users-h...@tomcat.apache.org>

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

Reply via email to