Comments on: Monitoring ActiveMQ Using JMX Over SSH

By: Luca

Luca — Fri, 16 Sep 2011 21:48:48 +0000

Thanks a lot mate, very helpful!

By: Benjamin Darfler

Benjamin Darfler — Thu, 04 Nov 2010 16:03:58 +0000

This is why I prefer to use AMQs built in connector which allows you to easily specify both ports as I pointed out in the article.

By: John Russell

John Russell — Thu, 04 Nov 2010 15:59:00 +0000

That is true. There is a blog I found which explains how to write a really simple agent class that you can pass to the JVM which allows you to set both of the ports.

http://olegz.wordpress.com/2009/03/23/jmx-connectivity-through-the-firewall/

By: zeno

zeno — Thu, 04 Nov 2010 15:40:53 +0000

Hi,

but what about the firewall. In this case your second port will not be fixeb, it will be negociated at runtime which is not ok for firewall.
How do you avoid this problem ?

By: Exposing a POJO as a JMX MBean easily with Spring « The Holy Java

Exposing a POJO as a JMX MBean easily with Spring « The Holy Java — Thu, 16 Sep 2010 13:26:23 +0000

[...] Monitoring ActiveMQ Using JMX Over SSH [...]

By: Felix Ehm

Felix Ehm — Tue, 24 Nov 2009 08:21:15 +0000

Sorry, forgot that tags have to be treated specially :

to disallow AMQ to create the connector :

…

By: Felix Ehm

Felix Ehm — Tue, 24 Nov 2009 08:16:59 +0000

Hi,

I’m with you if you report the lack of documentation. My additional info here is to set the port differently by disallowing AMQ to create the connector:

Instead, you let the connector be created explicitly by the JVM using (example):
-Dcom.sun.management.jmxremote.port=11119
-Dcom.sun.management.jmxremote.authenticate=true
-Dcom.sun.management.jmxremote.password.file=${ACTIVEMQ_BASE}/conf/jmx.password
-Dcom.sun.management.jmxremote.access.file=${ACTIVEMQ_BASE}/conf/jmx.access
(in the bin/activemq)

That’s how I got around this issue. This is also the solution to enable authentication/authorization if you want to avoid people to connect to your management console and mess around.

Cheers,
Felix

By: Benjamin Darfler

Benjamin Darfler — Fri, 20 Nov 2009 19:33:15 +0000

Glad it helped! That bit is the missing link that no one ever talks about.

By: Paul Borlin

Paul Borlin — Wed, 11 Nov 2009 16:39:41 +0000

Beauty, mate! I’ve wresting with this for too long. The missing link for me was the “-Djava.rmi.server.hostname=127.0.0.1″ switch. Most of the documentation I’ve seen was for running JConsole on the same machine as ActiveMQ, and I’m trying to do it remotely. Popped in my server’s name in place of 127.0.0.1, and wammo! Thanks for posting your pain.