Jens Deppe created GEODE-1318:
---------------------------------
Summary: JMX manager is not started immediately when
--bind-address is specified with 'start locator'
Key: GEODE-1318
URL: https://issues.apache.org/jira/browse/GEODE-1318
Project: Geode
Issue Type: Bug
Components: gfsh
Reporter: Jens Deppe
Just noticed the following. If I start a locator with:
{noformat}
$ gfsh start locator --name=locator1 --bind-address=127.0.0.1
{noformat}
And then immediately try and connect to JMX, I get an error:
{noformat}
gfsh> connect --jmx-manager=localhost[1099]
Connecting to Manager at [host=localhost, port=1099] ..
Could not find a GemFire jmx-manager service at [host=localhost, port=1099].
{noformat}
Indeed, using {{lsof}} there is nothing even listening on port {{1099}}.
However, if I connect to the locator first, the manager is magically started:
{noformat}
gfsh>connect --locator=localhost[10334]
Connecting to Locator at [host=localhost, port=10334] ..
Connecting to Manager at [host=10.118.33.250, port=1099] ..
Successfully connected to: [host=10.118.33.250, port=1099]
gfsh>disconnect
Disconnecting from: 10.118.33.250[1099]
Disconnected from : 10.118.33.250[1099]
gfsh>connect --jmx-manager=localhost[1099]
Connecting to Manager at [host=localhost, port=1099] ..
Successfully connected to: [host=localhost, port=1099]
{noformat}
This does not happen if I do not specify {{--bind-address}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
