Ok, and the value of the hc.mbean.name is used as the property "name" for the object name, right? So all HCs get the same fixed domain and type, they just differ by name.
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. If no one disagrees, I'll do the changes in the next days, along with using service properties. Carsten 2013/8/14 Bertrand Delacretaz <[email protected]> > On Wed, Aug 14, 2013 at 3:27 PM, Carsten Ziegeler <[email protected]> > wrote: > > ...maybe we should first answer the initial question :) Are all HC > > services registered as mbeans or not?... > > As I said I have at least one use case for making the MBeans > registration optional: when several HC are aggregated by a > CompositeHealthCheck (that executes several of them, selected by > tags), it might be good to expose only the composite as an MBean. > > The simplest seems to be to omit the MBean registration for HC > services that do not supply an hc.mbean.name property. > > -Bertrand > -- Carsten Ziegeler [email protected]
