On Wed, Aug 14, 2013 at 4:18 PM, Carsten Ziegeler <[email protected]> wrote: > Ok, and the value of the hc.mbean.name is used as the property "name" for > the object name, right?
Yes > So all HCs get the same fixed domain and type, they just differ by name. If you configure a name like foo/bar foo becomes the type, so you can set it. Might be better to have an explicit hc.mean.type service property. > > ...I already added a TODO to the jmx bridge, that we have to handle the case > where two HCs use the same "name". I think we should solve this by using > service ranking and only registering the one with the highest ranking.... Isn't that hard to troubleshoot? Generating a unique suffix for the second, instead of not registering it, might make it easier to detect the error. > > If no one disagrees, I'll do the changes in the next days, along with using > service properties. works for me. -Bertrand
