[CONF] Apache Camel > Why is my processor not showing up in JConsole

[confluence]

Why is my processor not showing up in JConsole Page edited by Claus Ibsen Changes (2) ... For example the minor ones such as {{setHeader}} does not and thus is not visible in JConsole. From *Camel 2.6* onwards your custom {{Processor}} can just implement {{ManagementAware}} and just return {{this}} in the method. Then you can use the Spring JMX annotations on your custom processor to have those attributes and operations enlisted in JMX. From *Camel 2.6* onwards your custom {{Processor}} should use the Spring JMX annotations. Just add {...@managedresource}} to the class, and the other annotations for the attributes and operations. Then Camel will automatic use those when the processor is being registered in JMX. {snippet:id=e1|lang=java|title=Custom processor|url="" ... Full Content Why is my processor not showing up in JConsole Not every processor is managed and thus not all is visible in the JConsole. A processor must implement the org.apache.camel.Service to be managed. Most EIP processors does this. For example the minor ones such as setHeader does not and thus is not visible in JConsole. From Camel 2.6 onwards your custom Processor should use the Spring JMX annotations. Just add @ManagedResource to the class, and the other annotations for the attributes and operations. Then Camel will automatic use those when the processor is being registered in JMX. Custom processor @ManagedResource("My Managed Component") public static class MyCustomProcessor implements Processor { private String foo = "hey"; @ManagedAttribute public String getFoo() { return foo; } @ManagedAttribute public void setFoo(String foo) { this.foo = foo; } public void process(Exchange exchange) throws Exception { exchange.getIn().setHeader("foo", getFoo()); } } See also Camel JMX Change Notification Preferences View Online | View Changes | Add Comment