geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Swapnil Bawaskar (JIRA)" <>
Subject [jira] [Created] (GEODE-1548) jmx-manager-hostname-for-clients not honored
Date Wed, 15 Jun 2016 20:35:09 GMT
Swapnil Bawaskar created GEODE-1548:

             Summary: jmx-manager-hostname-for-clients not honored
                 Key: GEODE-1548
             Project: Geode
          Issue Type: Bug
          Components: gfsh, management
            Reporter: Swapnil Bawaskar

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:
gfsh>start locator --name=locator --J=-Dgemfire.jmx-manager-hostname-for-clients=<public_ip>

When trying to connect to this locator from my laptop I get the following error:
gfsh>connect --locator=[10334]
Connecting to Locator at [host=, port=10334] ..
Connecting to Manager at [, port=1099]
Could not connect to : [, port=1099].
Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is
java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception
is: Connection reset]
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

View raw message