Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Complete
-
4.3.5, 4.2.12
-
None
Description
The stack trace is:
java.lang.RuntimeException: could not fork cache server at org.springframework.integration.gemfire.fork.ForkUtil.startCacheServer(ForkUtil.java:155) at org.springframework.integration.gemfire.fork.ForkUtil.cacheServer(ForkUtil.java:127) at org.springframework.integration.gemfire.inbound.CqInboundChannelAdapterTests.startUp(CqInboundChannelAdapterTests.java:74) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
The output to System.err appears to be related:
[FORK] Exception in thread "main" com.gemstone.gemfire.IncompatibleSystemException: Member bamboo-07(CacheServer:17649)<v12>:53948 could not join this distributed system because the existing member 10.194.6.19(CacheServer:25944)<v0>:8517 used the same name. Set the "name" gemfire property to a unique value. [FORK] at com.gemstone.gemfire.distributed.internal.DistributionManager.create(DistributionManager.java:626) [FORK] at com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:620) [FORK] at com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:281) [FORK] at com.gemstone.gemfire.distributed.DistributedSystem.connect(DistributedSystem.java:1651) [FORK] at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:227) [FORK] at org.springframework.integration.gemfire.fork.CacheServerProcess.main(CacheServerProcess.java:59)
Just a guess, but perhaps a previous cache server instance didn't shut down cleanly for some reason?
I'm pretty sure I've seen this with SI 4.2.x as well.