Re: [PROPOSAL] Add hostname-for-clients to ConfigurationProperties

2019-06-04 Thread Jinmei Liao
Thanks for the feedback. Both Dan and Juan pointed out how the hostname-for-clients are configured for each individual components currently: server/locator/gateway receivers are from gfsh commands options and jmx are from gemfire properties. Let me revise my original proposal to: Let's add a

Re: [PROPOSAL] Add hostname-for-clients to ConfigurationProperties

2019-06-04 Thread Juan José Ramos
Hello Jinmei, Applying this change will prevent users from using different NICs for different types of traffic, meaning that the same server won't be able to listen for JMX connections on *NIC1* and regular client-server connections on *NIC2*, right?. If my assumption is correct then we'd be

Re: [PROPOSAL] Add hostname-for-clients to ConfigurationProperties

2019-06-04 Thread Dan Smith
A user can configure the hostname-for-clients for locators and gateway receivers - they are part of the respective gfsh commands. Are you suggesting deprecating those settings as well, or just having a global property that is the default value if it is not overridden for a specific locator,

[PROPOSAL] Add hostname-for-clients to ConfigurationProperties

2019-06-04 Thread Jinmei Liao
We have "jmx-manager-hostname-for-clients" in the geode properties, we think it would be a good idea to deprecate that and use "hostname-for-clients" for the entire server. Currently we already need this property when launching a locator and start a gateway-receiver, and we have no way to