[
https://issues.apache.org/jira/browse/GEODE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Bawaskar reopened GEODE-746:
------------------------------------
The second part of this bug still needs to be fixed. When I tried to start a
locator using:
{noformat}
gfsh>start locator --name=l1 --bind-address=10.118.33.188
--J=-Dgemfire.jmx-manager-bind-address=10.118.33.188
--J=-Dgemfire.jmx-manager-hostname-for-clients=10.118.33.188
{noformat}
I got the below exception:
{noformat}
Please use "connect --locator=10.118.33.188[10334]" to connect Gfsh to the
locator.
Failed to connect; unknown cause: Connection refused to host: 192.168.1.181;
nested exception is:
java.net.ConnectException: Connection refused
{noformat}
When I use the {{java.rmi.server.hostname}} system property, I was able to
connect to the locator without any problem.
{noformat}
gfsh>start locator --name=l1 --bind-address=10.118.33.188
--J=-Dgemfire.jmx-manager-bind-address=10.118.33.188
--J=-Dgemfire.jmx-manager-hostname-for-clients=10.118.33.188
--J=-Djava.rmi.server.hostname=10.118.33.188
Starting a Geode Locator in
/Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/l1...
....
Locator in
/Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/l1
on 10.118.33.188[10334] as l1 is currently online.
Process ID: 26513
Uptime: 2 seconds
GemFire Version: 1.0.0-incubating-SNAPSHOT
Java Version: 1.8.0_45
Log File:
/Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/l1/l1.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true
-Dgemfire.load-cluster-configuration-from-dir=false
-Dgemfire.jmx-manager-bind-address=10.118.33.188
-Dgemfire.jmx-manager-hostname-for-clients=10.118.33.188
-Djava.rmi.server.hostname=10.118.33.188
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path:
/Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/lib/geode-core-1.0.0-incubating-SNAPSHOT.jar:/Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
Successfully connected to: JMX Manager [host=10.118.33.188, port=1099]
Cluster configuration service is up and running.
{noformat}
In summary, when a jmx-manager-bind-address is used, we should set the
{{java.rmi.server.hostname}} to the same value.
> 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
>
> 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)
