Camel has optional support for JMX management, which is part of the camel-management and camel-management-api JARs.

Using JMX to manage Apache Camel

The JMX instrumentation agent is enabled in Camel when the camel-management JAR is included in the classpath. Once enabled, the Camel runtime creates and registers MBean management objects with a MBeanServer instance in the VM. This allows Camel users to instantly obtain insights into how Camel routes perform down to the individual processor level.

The high level supported types of management objects are:

Most of these management objects also expose lifecycle operations in addition to performance counter attributes.

Disabling or enabling Camel JMX

JMX is only enabled in Camel when the camel-management JAR is included on the classpath. To quickly enable or disable JMX, simply add or remove this JAR from the classpath.

It is also possible to enable or disable JMX via configuration as documented below.

You can disable the JMX instrumentation agent by setting the Java VM system property as follows:


The property value is treated as boolean.

Alternatively, add a jmxAgent element inside the camelContext element in Spring XML configuration:

<camelContext id="camel" xmlns="">
  <jmxAgent id="agent" disabled="true"/>

In Java you can disable JMX directly on the CamelContext as follows:

CamelContext camel = new DefaultCamelContext();

Camel JMX configuration options

Camel JMX can be configured with the following options.

Option JVM System Property Default Value Description


required The JMX agent name




Whether to use the MBeanServer from JVM.




The default JMX domain of the MBeanServer




The JMX domain that all object names will use



Configures the level for which MBeans are registered. See section Registering MBeans for specific resources only for more details.




If this option is enabled then only processors with a custom id set will be registered. This allows you to filer out unwanted processors in the JMX console.



Configures the level for whether performance statistics is enabled for the MBean. See section Configuring level of granularity for performance statistics for more details.




Whether to include the hostname in the MBean naming.




Whether to use hostname or IP Address in the service url when creating the remote connector. By default the hostname will be used.




Whether load statistics is enabled (gathers load statistics using a background thread per CamelContext).




Whether endpoint runtime statistics is enabled (gathers runtime usage of each incoming and outgoing endpoints).




A flag that indicates whether to remove detected sensitive information (such as passwords) from MBean names and attributes.




Whether to allow updating routes at runtime via JMX using the ManagedRouteMBean. This is disabled by default, but can be enabled for development and troubleshooting purposes, such as updating routes in an existing running Camel via JMX and other tools.

Registering MBeans for specific resources only

Camel automatically registers MBeans for the context, routes, and processors when it starts up. However, you can specify a level to control whether or not MBeans are registered at startup. The levels are:

  • Default - Camel will register MBeans for the context, all the routes and the processors.

  • RoutesOnly - Camel will register MBeans for the context and for all the routes (not for any processor).

  • ContextOnly - Camel will register MBeans for the context (neither for any route nor for any processor).

Registering new MBeans for new routes, created by route templates, Kamelets

Camel provides the following settings to control when to register mbeans.

Option Default Description



If enabled then MBeans are always registered.



If enabled then adding new routes after CamelContext has been started will also register MBeans from that given route.



If enabled then adding routes created by Kamelet will also register MBeans from that given route.



If enabled then adding routes created by route template (not Kamelet, see option above) will also register MBeans from that given route.

By default, Camel automatically registers MBeans for all routes configured at startup. The registerNewRoutes option controls whether MBeans should also be registered for new routes added later on. This feature can be disabled, for example, if you are adding and removing temporary routes that do not require management.

In Camel 4.5 onwards there are additional options to configure whether routes created from route templates or Kamelets should be registered as MBeans or not. By default, Kamelets are now disabled with the intention to regard a Kamelet as a component, instead of a set of additional routes and processors MBeans that is essentially not needed for management and monitoring. The option registerRoutesCreateByKamelet can be set to true to enable MBeans which is how Camel 4.4 or older behaves. On the other hand routes created from route templates (not Kamelets) are default enabled.

However, be cautious when using the registerAlways option in conjunction with dynamic EIP patterns, such as the Recipient List, which have unique endpoints. This can potentially lead to system degradation due to the increasing number of MBeans in the registry from its associated services/producers. Keep in mind that an MBean is not a lightweight object and consumes memory.

Management naming pattern

You can configure a naming pattern for the MBeans names that Camel creates. The pattern is used as part of the ObjectName as the key after the domain name.

By default Camel will use MBean names for the ManagedCamelContextMBean as follows:


If you configure a name on the CamelContext then that name is part of the ObjectName as well. For example if we have:

<camelContext id="myCamel" ...>

Then the MBean names will be as follows:


In the event of a naming clash within the JVM, such as when there is already an MBean with the same name, Camel will automatically try to resolve the issue by finding a new, available name in the JMXMBeanServer using a counter. For example, the counter will be appended to the name, resulting in an ObjectName such as myCamel-1:


Naming Patterns

This is possible because Camel uses a naming pattern by default that supports the following tokens:

  • #camelId# = the CamelContext id (eg the name)

  • #name# - same as #camelId#

  • #counter# - an incrementing counter

  • #bundleId# - the OSGi bundle id (only for OSGi environments)

  • #symbolicName# - the OSGi symbolic name (only for OSGi environments)

  • #version# - the OSGi bundle version (only for OSGi environments)

The default naming pattern is differentiated between OSGi and non-OSGi as follows:

  • non OSGI: #name#

  • OSGi: #symbolicName#

If there is a naming clash in the JMXMBeanServer then Camel will automatically fallback and use the #counter# in the pattern to remedy this. Thus the following patterns will then be used:

  • non OSGI: #name#-#counter#

  • OSGi: #symbolicName#-#counter#

If you set an explicit naming pattern, then that pattern is always used, and the default patterns above are not used.

This allows us to have full control, very easily, of the naming for both the CamelContext id in the Registry and the JMX MBeans in the JMXMBeanRegistry.

So if we want to explicitly name both the CamelContext and to use fixed MBean names that do not change (i.e. without counters), then we can use the managementNamePattern attribute:

<camelContext id="myCamel" managementNamePattern="#name#">

Then the MBean names will always be as follows:


In Java, you can configure the managementNamePattern as follows:


Configuring performance statistics

You can set a level for whether performance statistics are enabled or not when Camel starts up. The levels are:

  • Default - Camel will enable statistics for both routes and processors (fine grained).

  • Extended - As default but with additional statistics gathered during runtime such as fine grained level of usage of endpoints and more.

  • RoutesOnly - Camel will only enable statistics for routes (coarse grained)

  • Off - Camel will not use any statistics.

What does statistics enabled mean?

Statistics enabled means that Camel will do fine grained performance statistics for that particular MBean. There are statistics you can see, such as: number of exchanges completed/failed, last/total/min/max/mean processing time, first/last failed time, etc.

Using Java DSL you set the statistics level by:

// only enable routes when Camel starts

And from XML DSL you can do:

<camelContext id="camel" xmlns="">
    <jmxAgent id="agent" statisticsLevel="RoutesOnly"/>

Performance load statistics

It is possible to include load statistics for CamelContext and Route MBeans. These statistics are for average load based on the number of in-flight exchanges, measured over periods of 1, 5, and 15 minutes. This is similar to load statistics on Unix systems.

You can enable this by setting loadStatisticsEnabled=true.

Hiding sensitive information

By default, Camel enlists MBeans in JMX such as endpoints configured using URIs. In this configuration, there may be sensitive information such as passwords.

This will mask URIs having options such as password and passphrase, and use xxxxxx as the replacement value.

Masking JMX attributes in custom components

When implementing custom Camel components you can mark which JMX attributes to mask with the @ManagedAttribute and @ManagedOperation annotations.

The mask attribute can be set to true to indicate that the result of this JMX attribute/operation should be masked (if enabled on JMX agent, see above).

For example, on the default managed endpoints from camel-core, we have declared that the EndpointUri JMX attribute is masked:

@ManagedAttribute(description = "Endpoint URI", mask = true)
String getEndpointUri();