[ https://issues.apache.org/jira/browse/GEODE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14598711#comment-14598711 ]
ASF subversion and git services commented on GEODE-51: ------------------------------------------------------ Commit 3c952ac5e5c948e09c7475170496a46da61ec190 in incubator-geode's branch refs/heads/develop from William Markito [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=3c952ac ] [GEODE-51] - Including hostname-for-client parameters for server startup in order allow external clients connect to a distributed system from a different network. Needed for VMs or Docker deployments > Property hostname-for-clients has an inconsistent behavior between server and > locator > ------------------------------------------------------------------------------------- > > Key: GEODE-51 > URL: https://issues.apache.org/jira/browse/GEODE-51 > Project: Geode > Issue Type: Bug > Components: client/server > Reporter: William Markito Oliveira > Assignee: William Markito Oliveira > > When running Geode on Docker I've discovered a couple problems with > hostname-for-clients property in order to allow external access to the > distributed system: > - When setting the property for servers through GFSH it seems to be ignored > and only works when using cache.xml. Note that GFSH setting does work for > locators. > - After specifying hostname-for-clients in cache.xml and attempting to > connect using Java API, although it doesn't throw an UnknownHostException but > returns 0 servers in the DS. Any operations on the regions return a > NoAvailableServersException. > Will discuss details with [~dschneider] and confirm the problem. -- This message was sent by Atlassian JIRA (v6.3.4#6332)