DZ3: JMX Instrumentation and Control

If you update the DZ runner shell script to its current form (just add -Dcom.sun.management.jmxremote to Java command line), you can use JConsole to monitor and control DZ3. This is what it looks like (click to enlarge):



And this is how to make it happen (see previous examples for context):

<!-- JMX configuration -->
<bean id="jmx-wrapper" class="net.sf.jukebox.jmx.JmxWrapper">
  <constructor-arg index="0" type="java.util.Set">
    <set>
      <ref bean="temperature_sensor-6EE055000000"/>
      <ref bean="temperature_sensor-cpu1"/>
      <ref bean="temperature_sensor-cpu2"/>
      <ref bean="temperature_sensor-mobo"/>
      <ref bean="temperature_sensor-sda"/>
      <ref bean="temperature_sensor-sdb"/>
      
      <ref bean="rrdlogger_sensors"/>
      <ref bean="rrdlogger_thermostats"/>
      <ref bean="rrdlogger_dampers"/>
    </set>
  </constructor-arg>
</bean>

Not all entities are JMX enabled at this time. Adding one to the configuration won't do any harm, but you'll get a warning message in the log.

It's worth mentioning that you need to add DZ3 classes to JConsole's classpath in order to get complex entities like DataSample<Double> rendered by JConsole, like this:

${JAVA_HOME}/bin/jconsole \
-J-Djava.class.path=${JAVA_HOME}/lib/jconsole.jar:\
${JAVA_HOME}/lib/tools.jar:$CLASSPATH

where CLASSPATH is the same that is used in DZ3 Runner.