Should I edit the doc directly?
I don't think I can do these things and the monitoring and the config
"restart" too. Certainly not by Aug 4.
415-1: mixes too many things. The MBeanServer is the
PlatformMBeanServer and is available. system-jmx-connector is a
separate issue, seems to be covered by 415-2
415-2:
- MBeans are loaded by calling the bootAMX() method on the loader (or
any CLI or GUI activity that does the same). There is no automatic
loading, by design.
- The jmxmp connector currently loads. Why must it be removed. It
finds an unused port if 8888 is used. It would be nice if it could
use @Configured to get the port.
- if the system support is used for jmx connector, how can we
configure that? The launcher has to set the right -D variables.
- authenticating management requests means we can't just use the
system connector I think. How would we hook into the connector?
Obviously it can be done, V2 code would need to be resurrected I guess.
On Jul 21, 2008, at 7:06 PM, Kedar Mhaswade wrote:
> 5. Lloyd -- 415-1 and 415-2 are new tasks. Please assess them.