I found the solution to my problem. The answer was unrelated to AMQ or JMX. It was due to weirdness in the /etc/hosts file on Red Hat Linux box. Fixing this, fixed RMI, which fixed JMX and all's well. More info can be found at:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=8092&postdays=0&postorder=asc&start=0 Christopher G. Stach II wrote: > > skimstercg wrote: >> On my local box, all I needed was to set useJmx="true" and uncomment the >> managementContext section of the conf/activemq.xml file. On my remote >> box's >> bin/activemq command I see: >> >> >> if [ -z "$SUNJMX" ] ; then >> #SUNJMX="-Dcom.sun.management.jmxremote.port=1616 >> -Dcom.sun.management.jmxremo >> te.authenticate=false -Dcom.sun.management.jmxremote.ssl=false" >> SUNJMX="-Dcom.sun.management.jmxremote" >> fi >> >> I'm assuming this is the how you turn on remote JMX monitoring. Now for >> a >> newbe question: what command line arg do I pass to turn this on. Thanks >> for >> the help. >> >> >> >> >> Christopher G. Stach II wrote: >>> skimstercg wrote: >>>> Doesn't work for me. Still get "Connection failed". >>> Did you enable remote JMX connection on AMQ's command line? >>> >>> -- >>> Christopher G. Stach II >>> >>> >>> >> > > http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html > > -- > Christopher G. Stach II > > > -- View this message in context: http://www.nabble.com/Use-JMX-to-monitor-remote-AMQ-tf2955761.html#a8441374 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
