Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Won't Do
-
None
-
None
-
None
Description
If you spin up an AWS instance, specify --J=-Djava.rmi.server.hostname=<public_ip>, and don't open incoming tcp connections for the JMX port in the AWS security group for that instance, the start locator command hangs indefinitely.
gfsh>start locator --name=l1 --J=-Djava.rmi.server.hostname=<public_ip>
Attachments
Attachments
Issue Links
- relates to
-
GEODE-1548 jmx-manager-hostname-for-clients not honored
- Reopened