Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

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

A processor must implement the org.apache.camel.Service to be managed. Most EIP processors does 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 automatic automatically use those when the processor is being registered in JMX.

...

The same applies when using beans in your routes.

...

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