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

["Jens Deppe (JIRA)" <ji...@apache.org>]

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

Jens Deppe commented on GEODE-746:
----------------------------------

Actually, there are two things wrong here. The first is simply the incorrect text being displayed.

The second is the message stating {{Failed to connect; unknown cause: Connection refused}}.

I believe what's happening is that the locator is connecting back to itself to check it's status. The problem becomes more evident when we bind the jmx manager to an address. At that point, gfsh will not be able to successfully connect to the JMX manager and will get an error like:
{noformat}
Connecting to Locator at [host=localhost, port=19991] ..
Connecting to Manager at [host=localhost, port=1099] ..
Connection refused to host: 192.168.1.28; nested exception is:
	java.net.ConnectException: Connection refused
{noformat}
This can be resolved by setting  {{java.rmi.server.hostname=127.0.0.1}} on the locator. We should consider setting {{java.rmi.server.hostname}} when using {{jmx-manager-bind-address}} (or just {{bind-address}}).

> 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: management
>            Reporter: Jens Deppe
>
> 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)