Other reasons: one could run multiple locators, and designate one for client connection and other for jmx.
-Anil. On Fri, Feb 24, 2017 at 2:20 PM, Galen M O'Sullivan <gosulli...@pivotal.io> wrote: > I can see that you might want to configure them separately, so it's good to > have both options. > > If I was to design this again, I think I would have the JMX address etc. > default to the same as the bind address, but as it is that would break > backwards compatibility. > > -Galen > > On Fri, Feb 24, 2017 at 1:40 PM, Anilkumar Gingade <aging...@pivotal.io> > wrote: > > > I believe they need to be separate, which helps to provide better control > > over application connection (who can connect to what)... > > > > They should all have default bind address, right? > > > > -Anil. > > > > > > On Fri, Feb 24, 2017 at 12:57 PM, Kevin Duling <kdul...@pivotal.io> > wrote: > > > > > When starting a locator, gfsh has the --bind-address option to tie to a > > > particular NIC. E.g., > > > > > > start locator --name=loc-sec > > > --security-properties-file=./security.properties > > > --classpath=/Users/kduling/gfsh-security --bind-address=localhost > > > > > > This address is the one the server uses to connect with. It doesn't > > affect > > > the JMX address, however. To do that, one has to do something like > this: > > > > > > gfsh start locator --name=locator1 --bind-address=192.168.1.45 > > > --J=-Dgemfire.jmx-manager-hostname-for-clients=192.168.1.45 > > > > > > There are several geode tickets that bring this topic up: > > > > > > GEODE-2364 > > > > > > GEODE-746 > > > > > > GEODE-1515 > > > > > > My question is, what is the expected behavior when using > --bind-address? > > > Should all services bind to that address and then be optionally > > overridden > > > by other flags such as --http-service-bind-address and > > > --hostname-for-clients? > > > > > >
