[
https://issues.apache.org/jira/browse/CAMEL-8531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-8531.
--------------------------------
Resolution: Fixed
There is also api to get the route mbean - which are the most common to use
> Make it easy to get the management mbean for a given process by its id
> ----------------------------------------------------------------------
>
> Key: CAMEL-8531
> URL: https://issues.apache.org/jira/browse/CAMEL-8531
> Project: Camel
> Issue Type: New Feature
> Components: camel-core, jmx
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.16.0
>
>
> As we primary have the performance stats and whatnot in JMX MBeans that are
> registered in the mbean server, end users would need to use the clunky JMX
> API to lookup the mbean for a process id.
> From Java code, you may just want to easily grab the mbean.
> For example:
> {code}
> ManagedAggregateProcessorMBean mbean =
> context.getManagedProcessor("myAggregator",
> ManagedAggregateProcessorMBean.class);
> {code}
> Then you have from java code, all the power of the mbean to get any kind of
> statistics you want, just like from JMX.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
