Pivotal Knowledge Base

Follow

To avoid IncompatibleSystemException with using same name

Environment

  • GemFire distributed system having multiple members

Symptom

When attempting to add members to a GemFire distributed system, the members fail to join and the following exception is logged:

[info 2014/06/17 10:49:25.206 JST DistributedLocking <main> tid=0x1] Now closing distribution for mylnx02(DistributedLocking:24954)<v42>:34265 Exception in thread "main" com.gemstone.gemfire.IncompatibleSystemException: Member mylnx02(DistributedLocking:24954)<v42>:34265 could not join this distributed system because the existing member mylnx01(DistributedLocking:24968)<v41>:33953 used the same name. Set the "name" gemfire property to a unique value.
at com.gemstone.gemfire.distributed.internal.DistributionManager.create(DistributionManager.java:628)
at com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:514)
at com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:229)
at com.gemstone.gemfire.distributed.DistributedSystem.connect(DistributedSystem.java:1105)
at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:227)
at quickstart.DistributedLocking.main(DistributedLocking.java:30)
        :

Cause

As described in the error message, there is an existing member with the same name as the member you are adding.

Fix

Set the "name" GemFire property to a unique value either in the gemfire.properties file or via API, i.e.:

Cache cache = new CacheFactory()
   .set("name", "DistributedLocking") // <=== here
   .set("cache-xml-file", "xml/DistributedLocking.xml")
   .create();

Comments

Powered by Zendesk