[CONF] Apache ActiveMQ > JMX
Title: Message Title Gary Tully edited a page Change comment: note on rmiServerPort JMX ... Property Name Default Value Description useMBeanServer true If true then it avoids creating a new MBean server if a MBeanServer has already been created in the JVM jmxDomainName org.apache.activemq The jmx domain that all objects names will use createMBeanServer true If we should create the MBeanServer is none is found. createConnector false Please refer to Java Management guide to configure the server for remote management and . Note: if set to true: lock down the endpoint serialisation with an appropriate jdk.serialFilter configure rmiServerPort and connectorHost to lock down the RMI server interface binding connectorPort 1099 The port that the JMX connector will use connectorHost localhost The host that the JMX connector and RMI server (if rmiServerPort>0) will use rmiServerPort 0 The RMI server port, handy if port usage needs to be restricted behind a firewall connectorPath /jmxrmi The path that JMX connector will be registered under findTigerMBeanServer true Enables/disables the searching for the Java 5 platform MBeanServer suppressMBean List of MBean name patters to ignore View page • Like Stop watching space • Manage notifications This message was sent by Atlassian Confluence 5.8.17
[CONF] Apache ActiveMQ > JMX
Title: Message Title Gary Tully edited a page JMX ... Property Name Default Value Description useMBeanServer true If true then it avoids creating a new MBean server if a MBeanServer has already been created in the JVM jmxDomainName org.apache.activemq The jmx domain that all objects names will use createMBeanServer true If we should create the MBeanServer is none is found. createConnector false Please refer to Java Management guide to configure the server for remote management and lock down the endpoint serialisation with an appropriate jdk.serialFilter connectorPort 1099 The port that the JMX connector will use connectorHost localhost The host that the JMX connector and RMI server (if rmiServerPort>0) will use rmiServerPort 0 The RMI server port, handy if port usage needs to be restricted behind a firewall connectorPath /jmxrmi The path that JMX connector will be registered under findTigerMBeanServer true Enables/disables the searching for the Java 5 platform MBeanServer suppressMBean List of MBean name patters to ignore View page • Like Stop watching space • Manage notifications This message was sent by Atlassian Confluence 5.8.17
[CONF] Apache ActiveMQ > JMX
Title: Message Title Gary Tully edited a page Change comment: add ref to the java management guide for remote jmx access JMX ... Apache ActiveMQ has extensive support for JMX to allow you to monitor and control the behavior of the broker via the JMX MBeans. AMQ Version >= 5.8.0 The MBean naming documented here applies to the 5.8.0 and later versions of ActiveMQ. Earlier versions of ActiveMQ used a variation of the naming; most, if not all, of the objects, attributes, and operations exist in those earlier versions, but the naming has changed. Using JMX to monitor Apache ActiveMQ ... 2. Run a JMX console Code Block $ jconsole 3. Connect to the given JMX URL: The ActiveMQ broker should appear in the list of local connections, if you are running JConsole on the same host as ActiveMQ. To connect to a remote ActiveMQ instance, or if the local process does not show up, use Remote Process option, and enter an URL. Here is an example localhost URL: Code Block service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi Info ActiveMQ logs the JMX url at INFO level during startup. JMX remote access Remote connections to JMX are not enabled by default in the activemq.xml for security reasons. Please refer to Java Management guide to configure the broker for remote management. Using the Apache ActiveMQ version on OS X it appears as follows: ... And you will be forced to login. Advanced JMX Configuration The activemq.xml configuration file allows you to configure how ActiveMQ is exposed to JMX for management. In some cases, you may need to tweak some of it's settings such as what port is used. Example: Code Block In 4.0.1 or later, on Java 1.5 or later we try and use the default platform MBeanServer (so that things like the JVM threads & memory settings are visible). If you wish to change the Java 5 JMX settings you can use various JMX system properties For example you can enable remote JMX connections to the Sun JMX connector, via setting the following environment variable (using set or export depending on your platform). These settings only configure the Sun JMX connector within Java 1.5+, not the JMX connector that ActiveMQ creates by default. Code Block ACTIVEMQ_SUNJMX_START=-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=1616 \ -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false (The ACTIVEMQ_SUNJMX_START environment variable is simple used by the "activemq" startup script, as additional startup parameters for java. If you start ActiveMQ directly, you'll have to pass these parameters yourself.) Selective MBean registration In situations where you need to scale your broker to large number of connections, destinations and consumers it can become very expensive to keep JMX MBeans for all those objects. Instead of turning off JMX completely, starting with 5.12.0, you can selectively suppress registration of some types of MBeans and thus help your broker scale, while still having a basic view of the broker state. ... Property Name Default Value Description useMBeanServer true If true then it avoids creating a new MBean server if a MBeanServer has already been created in the JVM jmxDomainName org.apache.activemq The jmx domain that all objects names will use createMBeanServer true If we should create the MBeanServer is none is found. createConnector true If we should create a JMX connector (to allow remote management) for the MBeanServerfalse Please refer to Java Management guide to configure the server for remote management connectorPort 1099 The port that the JMX connector will use connectorHost localhost The host that the JMX connector and RMI server (if rmiServerPort>0) will use rmiServerPort 0 The RMI server port, handy if port usage needs to be restricted behind a firewall connectorPath /jmxrmi The path that JMX connector will be registered under findTigerMBeanServer true Enables/disables the searching for the Java 5 platform MBeanServer suppressMBean List of MBean name patters to ignore View page • Like Stop watching space • Manage notifications This message was sent by Atlassian Confluence 5.8.17
[CONF] Apache ActiveMQ JMX
Dejan Bosanac edited the page: JMX ... (The ACTIVEMQ_SUNJMX_START environment variable is simple used by the activemq startup script, as additional startup parameters for java. If you start ActiveMQ directly, you'll have to pass these parameters yourself.) Selective MBean registration In situations where you need to scale your broker to large number of connections, destinations and consumers it can become very expensive to keep JMX MBeans for all those objects. Instead of turning off JMX completely, starting with 5.12.0, you can selectively suppress registration of some types of MBeans and thus help your broker scale, while still having a basic view of the broker state. For example, the following configuration will exclude all dynamic producers, consumers, connections and advisory topics from registering their MBeans Code Block language xml managementContext managementContext suppressMBean=endpoint=dynamicProducer,endpoint=Consumer,connectionName=*,destinationName=ActiveMQ.Advisory.*/ /managementContext ManagementContext Properties Reference Property Name Default Value Description useMBeanServer true If true then it avoids creating a new MBean server if a MBeanServer has
[CONF] Apache ActiveMQ JMX
Dejan Bosanac edited the page: JMX ... Code Block language xml managementContext managementContextmanagementContext suppressMBean=endpoint=dynamicProducer,endpoint=Consumer,connectionName=*,destinationName=ActiveMQ.Advisory.*/ /managementContext ... View Online Like View Changes Stop watching space Manage Notifications This message was sent by Atlassian Confluence 5.0.3, Team Collaboration Software
[CONF] Apache ActiveMQ JMX
Dejan Bosanac edited the page: JMX ... Code Block language xml managementContext managementContext suppressMBean=endpoint=dynamicProducer,endpoint=Consumer,connectionName=*,destinationName=ActiveMQ.Advisory.* / /managementContext ManagementContext Properties Reference ... View Online Like View Changes Stop watching space Manage Notifications This message was sent by Atlassian Confluence 5.0.3, Team Collaboration Software
[CONF] Apache ActiveMQ JMX
Dejan Bosanac edited the page: JMX ... Property Name Default Value Description useMBeanServer true If true then it avoids creating a new MBean server if a MBeanServer has already been created in the JVM jmxDomainName org.apache.activemq The jmx domain that all objects names will use createMBeanServer true If we should create the MBeanServer is none is found. createConnector true If we should create a JMX connector (to allow remote management) for the MBeanServer connectorPort 1099 The port that the JMX connector will use connectorHost localhost The host that the JMX connector and RMI server (if rmiServerPort0) will use rmiServerPort 0 The RMI server port, handy if port usage needs to be restricted behind a firewall connectorPath /jmxrmi
[CONF] Apache ActiveMQ JMX
Christopher L. Shannon edited the page:
JMX
...
3. Modify the activemq startup script (in bin) to enable the Java 1.5+ JMX connector
Find the ACTIVEMQ_SUNJMX_START= line and change it too the following: (note that in previous versions of ActiveMQ this property was called SUNJMX in some scripts. As of v5.12.0 all scripts use ACTIVEMQ_SUNJMX_START):
Code Block
1. Windows
ACTIVEMQ_SUNJMX_START=-Dcom.sun.management.jmxremote.port=1616 -Dcom.sun.management.jmxremote.ssl=false \
-Dcom.sun.management.jmxremote.password.file=%ACTIVEMQ_BASE%/conf/jmx.password \
-Dcom.sun.management.jmxremote.access.file=%ACTIVEMQ_BASE%/conf/jmx.access
2. Unix
ACTIVEMQ_SUNJMX_START=-Dcom.sun.management.jmxremote.port=1616 -Dcom.sun.management.jmxremote.ssl=false \
-Dcom.sun.management.jmxremote.password.file=${ACTIVEMQ_BASE}/conf/jmx.password \
-Dcom.sun.management.jmxremote.access.file=${ACTIVEMQ_BASE}/conf/jmx.access
...
Code Block
1. Windows
ACTIVEMQ_HOME=DRIVE_LETTER:/where/ActiveMQ/is/installed
ACTIVEMQ_BASE=%ACTIVEMQ_HOME%
ACTIVEMQ_SUNJMX_START=-Dcom.sun.management.jmxremote.port=1616 -Dcom.sun.management.jmxremote.ssl=false \
-Dcom.sun.management.jmxremote.password.file=%ACTIVEMQ_BASE%/conf/jmx.password \
-Dcom.sun.management.jmxremote.access.file=%ACTIVEMQ_BASE%/conf/jmx.access
2. Unix
ACTIVEMQ_HOME=DRIVE_LETTER:/where/ActiveMQ/is/installed
ACTIVEMQ_BASE=${ACTIVEMQ_HOME}
ACTIVEMQ_SUNJMX_START=-Dcom.sun.management.jmxremote.port=1616 -Dcom.sun.management.jmxremote.ssl=false \
-Dcom.sun.management.jmxremote.password.file=${ACTIVEMQ_BASE}/conf/jmx.password \
-Dcom.sun.management.jmxremote.access.file=${ACTIVEMQ_BASE}/conf/jmx.access
...
For example you can enable remote JMX connections to the Sun JMX connector, via setting the following environment variable (using set or export depending on your platform). These settings only configure the Sun JMX connector within Java 1.5+, not the JMX connector that ActiveMQ creates by default.
Code
[CONF] Apache ActiveMQ JMX
Arthur Naseef edited the page: JMX ... Apache ActiveMQ has extensive support for JMX to allow you to monitor and control the behavior of the broker via the JMX MBeans. AMQ Version = 5.8.0 The MBean naming documented here applies to the 5.8.0 and later versions of ActiveMQ. Earlier versions of ActiveMQ used a variation of the naming; most, if not all, of the objects, attributes, and operations exist in those earlier versions, but the naming has changed. Using JMX to monitor Apache ActiveMQ ... For xbean configuration Code Block broker useJmx=true brokerName=BROKER1 ... /broker ... To connect to a remote ActiveMQ instance, or if the local process does not show up, use Remote Process option, and enter an URL. Here is an example localhost URL: Code Block service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi ... For additional references provided below is a brief hierarchy of the mbeans and a listing of the properties, attributes, and operations of each mbeans. Mbean Type Properties / ObjectName Attributes Operations Broker
