...
(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 |
|
|
<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 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 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 |
