-
1. Re: TomcatClusteringCache's member attribute lists only one
brian.stansberry Nov 2, 2006 3:31 PM (in response to somejunk)What do you see in the console window that tells you there are two members? Are you sure it's not logging from the JGroups channel that's running from cluster-service.xml?
There's no difference in behavior in the cache's member attribute between a TCP config and a UDP config -- the cache knows nothing about the config; that's a JGroups detail. So if the member attribute is showing 2 members with UDP, that tells me that with TCP your caches aren't forming a cluster. -
2. Re: TomcatClusteringCache's member attribute lists only one
somejunk Nov 2, 2006 3:53 PM (in response to somejunk)[sb1585] New Members:1 ([ip address])
[sb1585] All Members:2 ([ip address node1], [ip address node2])
[TreeCache] viewAccepted(): new members:[node1:port number, node2:port number]
From these messages, I understood that they are in a cluster.
Is there any other way that we can verify if they are clustered or not?
Thanks -
3. Re: TomcatClusteringCache's member attribute lists only one
brian.stansberry Nov 2, 2006 4:23 PM (in response to somejunk)[TreeCache] viewAccepted(): new members:[node1:port number, node2:port number]
is the one you want; the other two don't count. Are you seeing that message with two members, and then when you look at the mbean you only see one? -
4. Re: TomcatClusteringCache's member attribute lists only one
somejunk Nov 2, 2006 6:55 PM (in response to somejunk)I am seeing that message on the node that I start first. whereas mbean for both nodes show only one member.