On 1/18/07, Manos Batsis <[EMAIL PROTECTED]> wrote:
Hi Guillaume, Thanks for your email. Guillaume Nodet wrote: > I think you need to reuse the existing JBoss jmx server. > I'm not sure how to locate the existing server. If the > <jmxServer /> tag fails to locate it, you may want to > create another server (reuse the existing rmi registry or > create a new one on another port). Is this URI supposed to lead to jsr160 implementation? JBoss does not implement that and thus there is no JMXServiceURL i can use AFAIK. On the other hand, i have a really blurry understanding of all this and may be totally out of scope here, which would be a good explanation of why -Dcom.sun.management.jmxremote does not work for me as an alternative on a 1.5 jdk. I will probably go back to the jboss deployer route as it just works. The reason for trying out WAR was to avoid container specific integration, but my impression is that is targeted in servlet containers. Advice from people that know better is welcome :-)
Yesterday I was able to deploy SMX to Tomcat successfully after simply setting the CATALINA_OPTS like so: CATALINA_OPTS="-Dcom.sun.management.jmxremote" This is as noted in the Tomcat docs here: http://tomcat.apache.org/tomcat-5.5-doc/monitoring.html Bruce -- perl -e 'print unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' Apache Geronimo - http://geronimo.apache.org/ Apache ActiveMQ - http://activemq.org/ Apache ServiceMix - http://servicemix.org/ Castor - http://castor.org/
