Nikolas Everett wrote:

You can do that.  See here:  http://logback.qos.ch/manual/jmxConfig.html  I typically change my logback configuration file on the file system then use jconsole to request that logback reload it.
You may have to jump through some hoops to get jconsole to connect to a running application server.  I stuff these in my .bashrc on development box to make it simple:
 CATALINA_OPTS="-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=8999 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.rmi.server.hostname=localhost"
 export CATALINA_OPTS
Thats about the lease secure way you could setup JMX, but it gets the job done for development.

AFAIK, JMX requires no configuration with JDK 1.6. After adding
<jmxConfigurator/> into logback.xml, you just run jconsole. Does your
experience differ?

Otherwise, if running under JDK 1.5, the steps you describe look good.