[jira] [Issue Comment Deleted] (GEODE-746) When starting a locator using --bind-address, gfsh prints incorrect connect message

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

     [ https://issues.apache.org/jira/browse/GEODE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jared Stewart updated GEODE-746:
--------------------------------
    Comment: was deleted

(was: To replicate this bug:

{code}
ssh -i /Users/jstewart/Downloads/management-and-monitoring.cer ubuntu@52.89.135.89
gfsh>start locator --name=l1
{code}
Now on your local machine:
{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}

Swap thinks that the following command ought to solve this problem, but right now when run on the AWS instance it simply hangs:

{code}
gfsh>start locator --name=l1 --J=-Djava.rmi.server.hostname=52.89.135.89
{code}






)

> When starting a locator using --bind-address, gfsh prints incorrect connect message
> -----------------------------------------------------------------------------------
>
>                 Key: GEODE-746
>                 URL: https://issues.apache.org/jira/browse/GEODE-746
>             Project: Geode
>          Issue Type: Improvement
>          Components: gfsh
>            Reporter: Jens Deppe
>            Assignee: Kevin Duling
>         Attachments: gfshThreadDump.txt, locatorThreadDump.txt
>
>
> When starting my locator with {{gfsh start locator --name=locator1 --port=19991 --bind-address=192.168.103.1}}, the output from gfsh looks like this:
> {noformat}
> ..............................
> Locator in /Users/jdeppe/debug/locator1 on 192.168.103.1[19991] as locator1 is currently online.
> Process ID: 2666
> Uptime: 15 seconds
> GemFire Version: 8.2.0.Beta
> Java Version: 1.7.0_72
> Log File: /Users/jdeppe/debug/locator1/locator1.log
> JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path: /Users/jdeppe/gemfire/82/lib/gemfire.jar:/Users/jdeppe/gemfire/82/lib/locator-dependencies.jar
> Please use "connect --locator=192.168.1.10[19991]" to connect Gfsh to the locator.
> Failed to connect; unknown cause: Connection refused
> {noformat}
> The connect string shown is just displaying my host address and not the bind address.



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