On Tue, Jun 9, 2009 at 12:02 PM, mrh<mrhayg...@gmail.com> wrote:
>
>
>
> bsnyder wrote:
>>
>>
>>
>> To completely disable JMX in ActiveMQ, you need to edit the ActiveMQ
>> startup script so that the com.sun.management.jmxremote property is
>> not set. This can be done by editing the bin/activemq script so that
>> the SUNJMX property is empty. Below are examples:
>>
>> Linux/Unix:
>>
>> SUNJMX=
>>
>> Windows:
>>
>> if "%SUNJMX%" == "" set SUNJMX=
>>
>
> Thanks for the quick reply, Bruce. I've updated the startup script, but I
> can still access run.jar from jconsole and also pull up the web admin page
> (http://localhost:8161/admin). Am I missing anything else?
Setting the SUNJMX environment variable to null does, in fact, disable
JMX. I've tested it myself using the following steps on Unix:
1) Expand a fresh copy of apache-activemq-5.2.0-bin.tar.gz
2) Edit the bin/activemq script to change the SUNJMX environment
variable from this:
SUNJMX="-Dcom.sun.management.jmxremote"
to this:
SUNJMX=
3) Start up ActiveMQ using the bin/activemq script
4) Start Jconsole and notice that the run.jar is not accessible via
JMX, nor is ActiveMQ accessible via the JMX URL
(service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi) via the Advanced
tab in Jconsole
This tells me that JMX is disabled.
As far as the web console goes that is a separate concern. If you want
to disable it you must comment out the webAppContext element from the
conf/activemq.xml file for the web console (it's within the jetty
element). This will prevent the admin web application from being
deployed.
Bruce
--
perl -e 'print
unpack("u30","D0G)u8...@4vyy9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder
