[jira] [Commented] (GEODE-1548) jmx-manager-hostname-for-clients not honored

["Jared Stewart (JIRA)" <ji...@apache.org>]

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

Jared Stewart commented on GEODE-1548:
--------------------------------------

I have reproduced this issue and it is still a problem.  Here are the steps to reproduce (note the AWS instance public ip I am using has public ip 52.89.135.89 and private ip 172.31.19.71).  

Start a locator in aws with the following command:
{code}
gfsh> start locator --name=l1 --J=-Dgemfire.jmx-manager-hostname-for-clients=52.89.135.89
{code}

Attempt to connect from your laptop:
{code}
gfsh>connect --locator=52.89.135.89[10334]

Connecting to Locator at [host=52.89.135.89, port=10334] ..

Connecting to Manager at [host=172.31.19.71, port=1099] ..

Could not connect to : [host=172.31.19.71, port=1099]. Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 172.31.19.71; nested exception is: 

    java.net.ConnectException: Operation timed out]
{code}

Notice that the client is attempting to connect to the private IP of the AWS instance, even though {{--J=-Dgemfire.jmx-manager-hostname-for-clients}} was specified.  

> jmx-manager-hostname-for-clients not honored
> --------------------------------------------
>
>                 Key: GEODE-1548
>                 URL: https://issues.apache.org/jira/browse/GEODE-1548
>             Project: Geode
>          Issue Type: Bug
>          Components: gfsh, management
>            Reporter: Swapnil Bawaskar
>            Assignee: Kevin Duling
>             Fix For: 1.0.0-incubating.M3
>
>
> While running Geode on AWS, found that {{jmx-manager-hostname-for-clients}} is not being honored resulting in not being able to connect to gfsh from outside AWS.
> I started a locator in AWS with the following command:
> {noformat}
> gfsh>start locator --name=locator --J=-Dgemfire.jmx-manager-hostname-for-clients=<public_ip> --hostname-for-clients=<public_ip>
> {noformat}
> When trying to connect to this locator from my laptop I get the following error:
> {noformat}
> gfsh>connect --locator=52.41.104.182[10334]
> Connecting to Locator at [host=52.41.104.182, port=10334] ..
> Connecting to Manager at [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099] ..
> Could not connect to : [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099]. Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
>     java.net.SocketException: Connection reset]
> {noformat}
> Note that gfsh is trying to connect to the public dns for the instance, not using the {{jmx-manager-hostname-for-clients}} property provided.



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