You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

Why is my processor not showing up in JConsole

Not every processor is managed, and thus not all are visible in JConsole.

A processor must implement the org.apache.camel.Service to be managed. Most EIP processors do 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 (for Camel 2.9 onwards see the tip box below). Just add @ManagedResource to the class, and the other annotations for the attributes and operations. Then Camel will automatically use those when the processor is being registered in JMX.

Error formatting macro: snippet: java.lang.NullPointerException

The same applies when using beans in your routes.

Error formatting macro: snippet: java.lang.NullPointerException

Camel 2.9 onwards provides Camel's own JMX annotations

Notice that from Camel 2.9 onwards its encouraged to use the @ManagedResource, @ManagedAttribute and @ManagedOperation from the org.apache.camel.api.management package. This allows your custom code to not depend on Spring JARs anymore.

See also

  • No labels