that does not exist at the moment, but it has come up before and it would be a nice enhancement. JMX becomes a bottleneck in a dynamic broker and disabling jmx altogether is not a viable option. I know in karaf 2.4/3.0 there is role based access control via an mbean server filter - maybe that provides a way to deny mbean creation. That may be a solution that would work today, the filter is installed on the jvm mbean server however afaik.
There is a single code entry point[1] for all mbean registration in the broker so gating that on a filter or regexp match may be all that we need. Can you please raise a enhancement JIRA to track this. [1] https://github.com/apache/activemq/blob/84c1419c3dbc5c8ba95629b11798ca05d4f14e37/activemq-broker/src/main/java/org/apache/activemq/broker/jmx/ManagementContext.java#L391 On 10 March 2015 at 09:38, Martin Lichtin <lich...@yahoo.com.invalid> wrote: > Wanted to ask if there's a way to disable MBeans creation for > sessions/producers/consumers in ActiveMQ? > > In certain setups (such as when using JTA/XA), not everything can be pooled, > and new producers/sessions are frequently created. This causes a constant > stream of new MBeans as well. > > James mentioned a way of disabling at > https://groups.google.com/d/msg/hawtio/VGgPbR99rcI/74XE-tZnSH8J > but I can't find any setting for that.
