Swapnil Bawaskar created GEODE-1548:
---------------------------------------
Summary: jmx-manager-hostname-for-clients not honored
Key: GEODE-1548
URL: https://issues.apache.org/jira/browse/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:
{noformat}
gfsh>start locator --name=locator
--J=-Dgemfire.jmx-manager-hostname-for-clients=<public_ip>
--hostname-for-clients=<public_ip>
{noformat}
When trying to connect to this locator from my laptop I get the following error:
{noformat}
gfsh>connect --locator=52.41.104.182[10334]
Connecting to Locator at [host=52.41.104.182, port=10334] ..
Connecting to Manager at
[host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099] ..
Could not connect to : [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com,
port=1099]. Failed to retrieve RMIServer stub:
javax.naming.CommunicationException [Root exception is
java.rmi.ConnectIOException: error during JRMP connection establishment; nested
exception is:
java.net.SocketException: Connection reset]
{noformat}
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
(v6.3.4#6332)
