geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-1141) Unable to retrieve cluster configuration from the locator
Date Tue, 29 Mar 2016 13:40:25 GMT

    [ https://issues.apache.org/jira/browse/GEODE-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216007#comment-15216007
] 

ASF subversion and git services commented on GEODE-1141:
--------------------------------------------------------

Commit c36591b73243c7ee3a0186710338453d12efe364 in incubator-geode's branch refs/heads/feature/GEM-534
from [~jens.deppe]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=c36591b ]

GEODE-1141: Catch and log Throwable on cluster config startup


> Unable to retrieve cluster configuration from the locator
> ---------------------------------------------------------
>
>                 Key: GEODE-1141
>                 URL: https://issues.apache.org/jira/browse/GEODE-1141
>             Project: Geode
>          Issue Type: Bug
>          Components: configuration
>            Reporter: Jens Deppe
>
> 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
> {noformat}
> 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
> {noformat}
> I am getting the below errors
> {code}
> 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)
> {code}
> 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. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message