2.10. Optimizing JMX Management

In situations where you need to scale your broker to a 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, however, you can selectively suppress registration of some types of MBeans and thus help your broker to scale, while still having a basic view of the broker state.

For example, the following configuration excludes all dynamic producers, consumers, connections and advisory topics, preventing them from registering their MBeans:

<managementContext>
<managementContext 
   suppressMBean="endpoint=dynamicProducer,endpoint=Consumer,connectionName=*,destinationName=ActiveMQ.Advisory.*"
>
</managementContext>

<managementContext>
<managementContext 
   suppressMBean="endpoint=dynamicProducer,endpoint=Consumer,connectionName=*,destinationName=ActiveMQ.Advisory.*"
>
</managementContext>