<br><br><div class="gmail_quote">On Wed, Jul 8, 2009 at 9:19 AM, Ceki Gulcu <span dir="ltr"><<a href="mailto:ceki@qos.ch">ceki@qos.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
<br>
Nikolas Everett wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You can do that. See here: <a href="http://logback.qos.ch/manual/jmxConfig.html" target="_blank">http://logback.qos.ch/manual/jmxConfig.html</a> I typically change my logback configuration file on the file system then use jconsole to request that logback reload it. <br>
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:<br>
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"<br>
export CATALINA_OPTS<br>
Thats about the lease secure way you could setup JMX, but it gets the job done for development.<br>
</blockquote>
<br></div>
AFAIK, JMX requires no configuration with JDK 1.6. After adding<br>
<jmxConfigurator/> into logback.xml, you just run jconsole. Does your<br>
experience differ?<br>
<br>
Otherwise, if running under JDK 1.5, the steps you describe look good.<div class="im"></div></blockquote><div><br>Without that JConsole would never connect. After a little more research, it looks like I had this problem because my `hostname` wasn't in /etc/hosts as 127.0.0.1. Once I fixed that I was able to connect without the CATALINA_OPTS. Let that be a lesson: always make sure your hostname resolves to 127.0.0.1 or weird stuff can break, like local JMX.<br>
<br>Nik Everett<br></div></div>