To answer my own questions:
On 04/09/2013 14:18, Willem Fibbe wrote:
> ...
> Now I was wondering 2 things:
> - if a Tomcat node restarts, will it be possible that it is trying to receive
> sessions from itself, rather than one or more of the other nodes? Or: should
> I configure a different server.xml on each node (its own member left out)?
I have setup a small cluster-group for testing (just quick testing) and have
seen a Tomcat node starting up,
replicating sessions from its own. Therefore, all our nodes now have a
different server.xml where its own node is
removed.
> - if I start Tomcat, I see in catalina.out:
> "WARNING:
> [SetPropertiesRule]{Server/Service/Engine/Cluster/Channel/Interceptor/Member}
> Setting property 'uniqueId' to '{10,0,10,227}' did not find a matching
> property."
> -> I removed uniqueId-attribute, but will this cause any possible
> problems?
So far, we have't seen any problems, although in catalina.out I see each server
with the same id:
INFO: Replication member
added:org.apache.catalina.tribes.membership.MemberImpl[tcp://hostname01.domain.nl:5678,hostname01.domain.nl,5678,
alive=0,id={0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 }, payload={}, command={},
domain={112 117 98 108 105 115 104 45 99 ...(15)}, ]
INFO: Replication member
added:org.apache.catalina.tribes.membership.MemberImpl[tcp://hostname02.domain.nl:5678,hostname02.domain.nl,5678,
alive=0,id={0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 }, payload={}, command={},
domain={112 117 98 108 105 115 104 45 99 ...(15)}, ]
Sessions seem te be replicating just fine though.
Willem
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
