[
https://issues.apache.org/jira/browse/GEODE-5731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845157#comment-16845157
]
Juan José Ramos Cassella commented on GEODE-5731:
-------------------------------------------------
The problem is not reproducible using the latest Geode version {{1.9.0}}. I've
also tried the scenario in AWS without any problems, both the locator and
server are accessible through their public DNS name when
{{hostname-for-clients}} is used.
The [pull request|https://github.com/apache/geode/pull/3614] adds some tests
and checks that the actual {{hostname}} returned through {{ServerLocation}} is
accurate and matches the {{hostname-for-clients}} used when starting the member.
> --hostname-for-client not working correclty
> -------------------------------------------
>
> Key: GEODE-5731
> URL: https://issues.apache.org/jira/browse/GEODE-5731
> Project: Geode
> Issue Type: Bug
> Components: configuration, locator
> Affects Versions: 1.6.0
> Reporter: Alexander Murmann
> Assignee: Juan José Ramos Cassella
> Priority: Major
> Labels: SmallFeature
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When starting a server cluster on EC2 and --hostname-for-client set for
> locator and server then the locator does not return the client-bind-address.
> Locator and server were initially started with
> {code:java}
> start locator --name=locator --port=41111
> --properties-file=./gemfire.properties --initial-heap=256M
> --hostname-for-clients=ec2-12-345-678-90.compute-1.amazonaws.com
> start server --name=server1 --server-port=44666
> --properties-file=./gemfire.properties --initial-heap=256M
> --start-rest-api=true --http-service-port=7676
> {code}
> After some debugging the hostname-for-client on the server was also set to be
> the public IP address.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
