[
https://issues.apache.org/jira/browse/GEODE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582682#comment-14582682
]
William Markito Oliveira commented on GEODE-51:
-----------------------------------------------
Looking at LauncherLifecycleCommands it seems like hostnameForClients is not
passed to ServerLauncher at startServer method. That address the different
behavior when starting the server using cacheXML vs command line.
Still troubleshooting why after the property is in place some channels are
still responding using internal IP and not the hostname for client value.
> 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)
