Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
If i start my locator using gfsh like
gfsh>start locator --name=locator
gfsh>start server --name=server1 --locators=localhost[10334]
it works fine.
But if I try to start the locator and server using LocatorLauncher and ServerLauncher classes like
java -cp ${GEMFIRE_HOME}/lib/gemfire.jar com.gemstone.gemfire.distributed.LocatorLauncher \ start locator \ --port=10334 \ --bind-address=10.112.204.114 java -cp ${GEMFIRE_HOME}/lib/gemfire.jar com.gemstone.gemfire.distributed.ServerLauncher \ start server \ -Dgemfire.locators=10.112.204.114[10334] \ -dir=server1 -properties-file=gemfire.properties
I am getting the below errors
java.io.EOFException: Locator at localhost(server:36010)<v1>:10334 did not respond. This is normal if the locator was shutdown. If it wasn't check its log for exceptions. at com.gemstone.org.jgroups.stack.tcpserver.TcpClient.requestToServer(TcpClient.java:125) at com.gemstone.org.jgroups.stack.tcpserver.TcpClient.requestToServer(TcpClient.java:78) at com.gemstone.gemfire.internal.cache.ClusterConfigurationLoader.requestConfigurationFromLocators(ClusterConfigurationLoader.java:171) at com.gemstone.gemfire.internal.cache.GemFireCacheImpl.requestAndApplySharedConfiguration(GemFireCacheImpl.java:866) at com.gemstone.gemfire.internal.cache.GemFireCacheImpl.init(GemFireCacheImpl.java:1017) at com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:682) at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:182) at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:229) at com.gemstone.gemfire.distributed.ServerLauncher.startWithGemFireApi(ServerLauncher.java:792) at com.gemstone.gemfire.distributed.ServerLauncher.start(ServerLauncher.java:694) at com.gemstone.gemfire.distributed.ServerLauncher.run(ServerLauncher.java:624) at com.gemstone.gemfire.distributed.ServerLauncher.main(ServerLauncher.java:194) Exception in thread "main" com.gemstone.gemfire.internal.cache.GemFireCacheImpl$4: cluster configuration service not available, caused by com.gemstone.gemfire.internal.process.ClusterConfigurationNotAvailableException: Unable to retrieve cluster configuration from the locator. at com.gemstone.gemfire.internal.cache.GemFireCacheImpl.requestAndApplySharedConfiguration(GemFireCacheImpl.java:879) at com.gemstone.gemfire.internal.cache.GemFireCacheImpl.init(GemFireCacheImpl.java:1017) at com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:682) at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:182) at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:229) at com.gemstone.gemfire.distributed.ServerLauncher.startWithGemFireApi(ServerLauncher.java:792) at com.gemstone.gemfire.distributed.ServerLauncher.start(ServerLauncher.java:694) at com.gemstone.gemfire.distributed.ServerLauncher.run(ServerLauncher.java:624) at com.gemstone.gemfire.distributed.ServerLauncher.main(ServerLauncher.java:194) Caused by: com.gemstone.gemfire.internal.process.ClusterConfigurationNotAvailableException: Unable to retrieve cluster configuration from the locator. at com.gemstone.gemfire.internal.cache.ClusterConfigurationLoader.requestConfigurationFromLocators(ClusterConfigurationLoader.java:186) at com.gemstone.gemfire.internal.cache.GemFireCacheImpl.requestAndApplySharedConfiguration(GemFireCacheImpl.java:866)
The issue is also faced by customer who were using com.gemstone.gemfire.internal.SystemAdmin class to start locator and servers.
If they use gfsh scripts to run the locator and programatically start serves it works fine.