If you're talking about GFSH commands only... removing JMX manager options
from "start server" then that's probably reasonable.
But as John described better than me, I wouldn't make
non-dedicated-locators unable to host certain services such as JMX manager
or locator.
For example, it wasn't easy
What you described is a consequence of its current design/implementation, a
tightly coupled one at that.
* Why does the "Configuration Service" have to be limited to *Locators*?
* Likewise, why would a "Management Service" be limited to *Managers*?
I think of the later (*Locators/Managers*) as "
One thing that prompted this initial proposal is that our (management and
monitoring) service boundaries, (or one could say APIs), are not well
defined.
Case in point; we currently have a 'configuration service' which is used to
persist configuration. This service is only available on locators. Th
Typo; Sorry!
This..
> I may even launch and connect additional servers using Gfsh within my IDE
(or using *Gfsh*) that are connected to my *Boot* server, particularly if
that *Boot* server also embeds a *Locator*.
should have read...
> I may even launch and connect additional servers *within my
Most of the geode developers are working to get rid of singleton calls (and
next up static code) with the goal of being able to have multiple Cache
instances in one JVM. This is to facilitate writing geode and geode
application tests in one JVM. This fits in with what John is saying as well.
Basic
Hi Jinmei-
Plain and simple, "development purposes". I can easily debug such a server
when I can launch it from my IDE and I can still inspect the server using
*Gfsh*. I may even launch and connect additional servers using Gfsh within
my IDE (or using *Gfsh*) that are connected to my *Boot* serv
Hi, John, what's the intended usage of this jmx-manager on the
cache-server when app developers started a cache-server that way in spring
boot? Is that usually for pulse or other jmx client for monitoring purpose
mostly? Or they would still want to connect using gfsh and execute bunch of
commands
So long as we **never** remove the ability to start an "embedded"
*Locator/Manager* in an [application] *CacheServer *process*, *which is
highly valuable during "*development*".
For instance, I may want to spin up an application peer *CacheServer* instance
with an embedded *Locator/Manager*, like
TL;DR I'd like to propose that we deprecate and ultimately remove the
ability to run a JMX manager on a non-locator member.
I'm not sure about the history for this capability and the original use
cases but I imagine it would have been driven, to a large part, by the
ability for member discovery wi
