geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jens Deppe (JIRA)" <>
Subject [jira] [Commented] (GEODE-1935) gfsh start locator command prints endless dots when starting inside docker
Date Mon, 03 Oct 2016 18:20:20 GMT


Jens Deppe commented on GEODE-1935:

I've looked at this a bit and can get to a partial solution. When running a locator instance
in a Docker container I first start the container and expose ports {{1099}} (default JMX port)
and {{10334}} (default locator port). Then I start gfsh with this command:
gfsh start locator --name=locator1 \ \
  --J=-Djava.rmi.server.hostname=localhost \

Notice the use of {{}}. This forces all "ephemeral"
RMI client stub ports to be the specified port. With this config I can connect to the locator
from the docker host. {{gfsh -e "connect locator=localhost[10334]"}}.

However, this limits the use of gfsh to the docker host. When I try and replace {{localhost}},
in the above gfsh command, with my host's local IP, I get similar behavior to the original
bug. The problem appears to be that there is still some use of ephemeral ports which prevents
this. Of interest is debugging into {{MBeanProcessController.getJMXServiceURL}} and the eventual
{{connect}} deep inside RMI. More investigation is required...

> gfsh start locator command prints endless dots when starting inside docker
> --------------------------------------------------------------------------
>                 Key: GEODE-1935
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Abhijat Upadhyay
>         Attachments:
> I have built a docker container using gemfire When I try to start locator it
keeps printing endless dots. I read about this @
and thus using gemfire I raised a ticket for Pivotal as well
but since it is an issue I see inside docker, and they do not officially support dockerized
gemfire yet, I thought I will report it here as well.
> I see that you have containerized gemfire as well on github source repo but not sure
if you have seen this issue. I can provide you with my source code as well if that helps in
reproducing this issue.
> Any help/guidance is much appreciated.
> Thank you,
> AU
> ======================
> I have attached my docker project with this ticket. And instructions to run it are given
in the "Comments" section below.

This message was sent by Atlassian JIRA

View raw message