[
https://issues.apache.org/jira/browse/CAMEL-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507270#comment-13507270
]
Claus Ibsen commented on CAMEL-5780:
------------------------------------
This is current by design as only processors from routes is enlisted in JMX.
There is some limitations in Camel 2.x when it comes to interceptors etc.
We will address this in Camel 3.0, when we re-architect some internal pieces.
When we get around that, then possible we can have JMX for processors in
interceptors etc.
> JMX statistics problem when intercept() followed with process()
> ---------------------------------------------------------------
>
> Key: CAMEL-5780
> URL: https://issues.apache.org/jira/browse/CAMEL-5780
> Project: Camel
> Issue Type: Bug
> Components: camel-core, jmx
> Affects Versions: 2.10.2
> Reporter: Meifang Shen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.11.0
>
> Attachments: ProcessorAfterIntercept.jpg
>
>
> Here is the test class:
> {noformat}
> intercept().id("Intercept_1").process(new Processor() {
>
> public void process(Exchange exchange) throws Exception {
> System.out.println("Intercept occurs");
> }
> }).id("Intercept_Processor");
> from("timer:foo?period=1000&repeatCount=2").id("from_1").process(new
> Processor() {
>
> public void process(Exchange exchange) throws Exception {
> System.out.println("normal route processor");
> }
> }).id("route_Processor1");
> from("timer:foo?period=1000&repeatCount=2").id("from_2").process(new
> Processor() {
>
> public void process(Exchange exchange) throws Exception {
> System.out.println("normal route processor");
> }
> }).id("route_Processor2");
> {noformat}
> The MBean "org.apache.camel/processors/***/" has no processor
> "Intercept_Processor", only has other two.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
