If you run one cache/cache manager on some arbitrary VM and then run a completely different cache/cachemanager on another VM in the same network, JGroups messages will show up for the other cache that you do not care about, making it difficult to decipher what is going on with your own cache.
Hello John, it would be helpful to have example logs. What messages you think were not supposed to be in the logs etc.
11:00:15,317 DEBUG [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,josborne-jdg131-6617) New view accepted: [josborne-jdg131-6617|4] (3) [josborne-jdg131-6617, josborne-jdg132-56382, josborne-jdg133-16837] 11:00:15,318 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,josborne-jdg131-6617) ISPN000094: Received new cluster view: [josborne-jdg131-6617|4] (3) [josborne-jdg131-6617, josborne-jdg132-56382, josborne-jdg133-16837] Here are a couple samples I took from josborne-jdg131. Note that josborne-jdg133 has the same jgroups.xml file but is running a completely different cache configuration.
Hey John, JDG is working as expected. Your nodes are clustering with each other, since they share the same JGroups configuration. You are just running different caches on each node. Running asymmetric caches is a supported use case in JDG 6.2. Thanks, Alan
OK thanks. From the logs it looked like their might be some sort of unauthorized communication between the two caches.
These messages are just showing that you have 3 nodes in your cluster view, so nothing spurious going on!