...
Apache Camel has extensive support for JMX to allow you to monitor and control the Camel managed objects with a JMX client.
Camel also provides a JMX component that allows you to subscribe to MBean notifications. This page is about how to manage and monitor Camel using JMX.
Activating JMX in Camel
| Table of Contents |
|---|
...
Spring JAR
...
Dependencies Required By Camel 2.8 or
...
Older
The following Spring jar files must be on the classpath in order for Camel to be able to use JMX instrumentation:
spring-context.jar
...
spring-aop.jar
...
spring-beans.jar
...
spring-core.jar
...
If these jar files are not on the classpath
...
Camel will fallback to non JMX mode.
...
Camel will log a warning to this affect using the logger: org.apache.camel.impl.DefaultCamelContext.
From Camel 2.9
...
: the Spring
...
jar files are no longer required for Camel to run
...
in JMX mode.
Using JMX to manage Apache Camel
By default, JMX instrumentation agent is enabled in Camel, which means that 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 DefaultManagementNamingStrategy is the default naming strategy which builds object names used for MBean registration. By default , org.apache.camel is the domain name for all object names created by CamelNamingStrategy. The domain name of the MBean object can be configured by Java VM system property:
...
Or, by adding a jmxAgent element inside the the camelContext element in Spring configuration:
...
...
Spring configuration always takes precedence over system properties when they both present. It is true for all JMX related configurations.
...
You can disable JMX instrumentation agent by setting the Java VM system property as follow. The property value is treated as boolean.
...
Or, by adding a jmxAgent element inside the camelContext element in Spring configuration:
...
...
Or in Camel 2.1 its a bit easier (not having to use JVM system property) if using pure Java as you can disable it as follows:
...
...
Locating a MBeanServer in the Java VM
Each CamelContext can have an instance of InstrumentationAgent wrapped inside the InstrumentationLifecycleStrategy. The InstrumentationAgent is the object that interfaces with a MBeanServer to register/unregister Camel MBeans. Multiple CamelContexts/InstrumentationAgents can/should share a MBeanServer. By default, Camel runtime picks the first MBeanServer returned by MBeanServerFactory.findMBeanServer method that matches the default domain name of org.apache.camel. You may want to change the default domain name to match the MBeanServer instance that you are already using in your application. Especially, if your MBeanServer is attached to a JMX connector server, you will not need to create a connector server in Camel.
You can configure the matching default domain name via system property.
...
Or, by adding a a jmxAgent element inside the the camelContext element in Spring configuration:
...
If no matching MBeanServer can be found, a new one is created and the new MBeanServer's default domain name is set according to the default and configuration as mentioned above.
It is also possible to use the PlatformMBeanServer when it is desirable to manage JVM MBeans by setting the system property. The MBeanServer default domain name configuration is ignored as it is not applicable.
From Camel Starting in next release ( 1.5), : the default value of usePlatformMBeanServer will be changed to "True". You can set is true. Set the property to false to "False" to disable using platform MBeanServer.
...
...
Or, by adding a a jmxAgent element inside the camelContext element in Spring configuration:
...
Creating JMX RMI Connector Server
JMX connector server enables MBeans to be remotely managed by a JMX client such as JConsole; Camel JMX RMI connector server can be optionally turned on by setting system property and the MBeanServer used by Camel is attached to that connector server.
...
...
Or, by adding a jmxAgent element inside the camelContext element in Spring configuration:
...
JMX Service URL
The default JMX Service URL has the format:
...
where registryPort is the RMI registry port and the default value is 1099.
You can set the RMI registry port by system property.
...
Or, by adding a jmxAgent element inside the the camelContext element in Spring configuration:
...
where serviceUrlPath is the path name in the URL and the default value is /jmxrmi/camel.
You can set the service URL path by system property.
...
...
...
From Camel 2.4
...
: various options can also be set
...
on the ManagementAgent:
...
Or, by adding a a jmxAgent element inside the the camelContext element in Spring configuration:
...
By default, RMI server object listens on a dynamically generated port, which can be a problem for connections established through a firewall. In such situations, RMI connection port can be explicitly set by the system property.
...
...
Or , by adding a a jmxAgent element inside the camelContext element in Spring configuration:
...
...
When the connector port option is set, the JMX service URL will become:
...
...
System Properties for Camel JMX
...
Support
Property Name | value | Description |
|---|---|---|
|
| if is true , it will enable jmx feature When |
See more system properties in this section below: jmxAgent Properties Reference
...
See this page for details about enabling JMX in Tomcat.
In short, modify your your catalina.sh (or or catalina.bat in Windows) file to set the following options...
...
...
JBoss AS 4
By default JBoss creates its own MBeanServer. To allow Camel to expose to the same server follow these steps:1.
- Tell Camel to use the Platform
MBeanServer(This defaults to true in Camel 1.5)
...
...
...
- Alter your JBoss instance to use the Platform
MBeanServer. - Add the following property to
...
- your
JAVA_OPTSby
...
- editing
run.sh
...
- or
run.conf
...
-Djboss.platform.mbeanserver
...
WebSphere
Alter the mbeanServerDefaultDomain to be "be WebSphere"
...
Oracle OC4j
The Oracle OC4J J2EE application server will not allow Camel to access the platform MBeanServer. You can identify this in the log as Camel will log a WARNING WARN.
...
To resolve this you should disable the JMX agent in Camel, see section Disabling JMX instrumentation agent in Camel
...
The Spring configuration file allows you to configure how Camel is exposed to JMX for management. In some cases, you could specify more information here, like the connector's port or the path name.
Example:
...
If you wish to change the Java 5 JMX settings you can use various JMX system properties
For example you can enable remote JMX connections to the Sun JMX connector, via setting the following environment variable (using set or export depending on your platform). These settings only configure the Sun JMX connector within Java 1.5+, not the JMX connector that Camel creates by default.
...
(The The SUNJMX environment variable is simple used by the startup script for Camel, as additional startup parameters for the JVM. If you start Camel directly, you'll have to pass these parameters yourself.)
...
Spring property | System property | Default Value | Description | ||
|---|---|---|---|---|---|
|
|
| The JMX agent name, and it is not optional. | ||
|
|
| If | ||
|
|
| The default JMX domain of the | ||
|
|
| The JMX domain that all object names will use. | ||
|
|
| If we should create a JMX connector (to allow remote management) for the | ||
|
|
| The port that the JMX RMI registry will use. | ||
|
| -1 (dynamic) | The port that the JMX RMI server will use. | ||
|
|
| The path that JMX connector will be registered under. | ||
|
|
| Camel 2.0: 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. | ||
|
|
| Camel 2.1: Configures the level for whether performance statistics is enabled for the MBean. See section Configuring level of granularity for performance statistics for more details. From Camel 2.16: the | ||
|
|
|
|
| Camel 2.13: Whether to include the hostname in the MBean naming. From Camel 2.13 onwards this : the default is default You can use this option to restore old behavior if really needed. |
Configuring whether to register MBeans always, for new routes or just by default
Available as of Camel 2.7
Camel now offers 2 settings to control whether or not to register mbeans
Option | Default | Description |
|---|---|---|
|
| If enabled then MBeans is always registered. |
|
| If enabled then adding new routes after CamelContext has been started will also register MBeans from that given route. |
|
|
| Camel 2.16: Whether to use hostname or IP Address in the service url when creating the remote connector. By default the hostname will be used. |
|
|
| Camel 2.16:Whether load statistics is enabled (gathers load statistics using a background thread per CamelContext). |
|
|
| Camel 2.16: Whether endpoint runtime statistics is enabled (gathers runtime usage of each incoming and outgoing endpoints). |
Configuring Whether to Register MBeans always, For New Routes or Just by Default
Available as of Camel 2.7
Camel now offers 2 settings to control whether or not to register mbeans
Option | Default | Description |
|---|---|---|
|
| If enabled then MBeans is always registered. |
|
| If enabled then adding new routes after CamelContext has been started will also register MBeans from that given route. |
By default Camel registers MBeans for all the routes configured when its starting. The registerNewRoutes option control if MBeans should also be registered if you add new routes thereafter. You can disable By default Camel registers MBeans for all the routes configured when its starting. The registerNewRoutes option control if MBeans should also be registered if you add new routes thereafter. You can disable this, if you for example add and remove temporary routes where management is not needed.
Be a bit caution to use the registerAlways option when using dynamic EIP patterns such as the Recipient List having unique endpoints. If so then each unique endpoint and its associated services/producers would also be registered. This could potential lead to degradation in system degration performance due the rising number of mbeans in the registry. A MBean is not a light-weight object and thus consumes memory.
...
Using JConsole to monitor Camel
The CamelContext should appear in the list of local connections, if you are running JConsole on the same host as Camel. To connect to a remote Camel instance, or if the local process does not show up, use Remote Process option, and enter an URL.
Here is an example localhost URL: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi/camel
Using the Apache Camel with JConsole
...
Which endpoints are registered
In Camel 2.1 onwards onward only singleton endpoints are registered as the overhead for non singleton will be substantial in cases where thousands or millions of endpoints are used. This can happens when using a Recipient List EIP or from a ProducerTemplate that sends a lot of messages.
...
The Camel notification events give a coarse grained overview what is happening. You can see lifecycle event from context and endpoints and you can see exchanges being received by and sent to endpoints. From Camel 2.4 you can use a custom JMX NotificationListener to listen the camel events.
First you need to set up a a JmxNotificationEventNotifier before you start the CamelContext.
...
...
Second you can register your listener for listening the event
...
Using the Tracer MBean to get fine grained tracing
Additionally to the coarse grained notifications above Camel 2.9.0 support JMX Notification for fine grained trace events.
These can be found in the Tracer MBean. To activate fine grained tracing you first need to activate tracing on the context or on a route.
This can either be done when configuring the context or on the context / route MBeans.
As a second step you have to set the jmxTraceNotifications attribute to true on the tracer. This can again be done when configuring the context or at runtime run time on the tracer MBean.
Now you can register for for TraceEvent Notifications on the Tracer MBean using JConsole. There will be one Notification for every step on the route with all exchange and message details.
...
Available as of Camel 2.0
You can decorate your own endpoints with Spring managed annotations @ManagedResource to allow to register them in the Camel MBeanServer and thus access your custom MBeans using JMX.
Notice: in Camel 2.1 we have changed this to apply other than just endpoints but then you need to implement the interface org.apache.camel.spi.ManagementAware as well. More about this later.
For example we have the following custom endpoint where we define some options to be managed:
...
...
Notice from From Camel 2.9 onwards its encouraged to : it's encouraged that you use the @ManagedResource, @ManagedAttribute, and @ManagedOperation attributes from the org.apache.camel.api.management package. This allows your custom code to not depend on Spring JARs.
...
Camel now offers to use your own MBeans when registering services for management. What that means is for example you can develop a custom Camel component and have it expose MBeans for endpoints, consumers and producers etc. All you need to do is to implement the interface org.apache.camel.spi.ManagementAware and return the managed object Camel should use.
Now before you think oh boys the JMX API is really painful and terrible, then yeah you are right. Lucky for us Spring though too and they created a range of annotations you can use to export management on an existing bean. That means that you often use that and just return this in the getManagedObject from the ManagementAware interface. For an example see the code example above with the CustomEndpoint.
Now in Camel 2.1 you can do this for all the objects that Camel registers for management which are quite a bunch, but not all.
For services which do not implement this ManagementAware interface then Camel will fallback to using default wrappers as defined in the table below:
Type | MBean wrapper |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In addition to that there are some extended wrappers for specialized types such as
Type | MBean wrapper |
|---|---|
|
|
|
|
|
|
|
|
|
|
And in the future we will add additional wrappers for more EIP patterns.
...
Camel provides a pluggable API for naming strategy by org.apache.camel.spi.ManagementNamingStrategy. A default implementation is used to compute the MBean names that all MBeans are registered with.
...
Available as of Camel 2.10
From Camel 2.10 onwards : we made it easier to configure a naming pattern for the MBeans. The pattern is used as part of the ObjectName as they key after the domain name. By default Camel will use MBean names for the ManagedCamelContextMBean as follows:
...
And from From Camel 2.13 onwards the : the hostname is not included in the MBean names, so the above example would be 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
...
Then the MBean names will be as follows:
...
Now if there is a naming clash in the JVM, such as there already exists a MBean with that given name above, then Camel will by default try to auto correct this by finding a new free name in the JMXMBeanServer by using a counter. As shown below the counter is now appended, so we have myCamel-1 as part of the ObjectName:
...
...
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:
#bundleId#-#name# - OSGi Camel 2.13:
#symbolicName#
However if there is a naming clash in the JMXMBeanServer then Camel will automatic fallback and use the #counter# in the pattern to remedy this. And thus the following patterns will then be used:
- non OSGI:
#name#-#counter# - OSGi:
#bundleId#-#name#-#counter# - OSGi Camel 2.13:
#symbolicName#-#counter#
If you set an explicit naming pattern, then that pattern is always used, and the default patterns above is not used.
This allows us to have full control, very easily, of the naming for both the CamelContext id in the Registry as well the JMX MBeans in the JMXMBeanRegistry.the JMXMBeanRegistry.
From Camel 2.15 onwards you can configure the default management name pattern using a JVM system property, to configure this globally for the JVM. Notice that you can override this pattern by configure it explicit, as shown in the examples further below.
Set a JVM system property to use a default management name pattern that prefixes the name with cool.
...
So if we want to explicit name both the CamelContext and to use fixed MBean names, that do not change (eg e.g., has no counters), then we can use the new managementNamePattern attribute:
...
...
Then the MBean names will always be as follows:
...
In Java, you can configure the managementNamePattern as follows:
...
...
You can also use a different name in the managementNamePattern than the id, so for example we can do:
...
You may want to do this in OSGi environments in case you do not want the OSGi bundle id as part of the MBean names. As the OSGi bundle id can change if you restart the server, or uninstall and install the same application. You can then do as follows to not use the OSGi bundle id as part of the name:
...
...
Note this requires that myCamel is unique in the entire JVM. If you install a 2nd Camel application that has the same CamelContext id and managementNamePattern then Camel will fail upon starting, and report a MBean already exists exception.
...
Camel now provides a totally pluggable management strategy that allows you to be 100% in control of management. It is a rich interface with many methods for management. Not only for adding and removing managed objects from the MBeanServer, but also event notification is provided as well using the org.apache.camel.spi.EventNotifier API. What it does, for example, is make it easier to provide an adapter for other management products. In addition, it also allows you to provide more details and features that are provided out of the box at Apache.
...
You can now set a pre set level whether performance statistics is enabled or not when Camel start ups. The levels arewhen Camel start ups. The levels are
Extended- As default but with additional statistics gathered during runtime such as fine grained level of usage of endpoints and more. This options requires Camel 2.16 *- All / Default
Alldefault - Camel will enable statistics for both routes and processors (fine grained). From Camel 2.16: theAlloption was renamed toDefault. RoutesOnly- Camel will only enable statistics for routes (coarse grained)Off- Camel will not enable statistics for any.
From Camel 2.9 onwards the performance statistics also include average load statistics per CamelContext and Route MBeans. The statistics is average load based on the number of in-flight exchanges, on a per 1, 5, and 15 minute rate. This is similar to load statistics on Unix systems. Camel 2.11 onwards allows you to explicit disable load performance statistics by setting loadStatisticsEnabled=false on the <jmxAgent>. Note that it will be off if the statics level is configured to off as well. From Camel 2.13 onwards the load performance statistics is by default disabled. You can enable this by setting loadStatisticsEnabled=true on the <jmxAgent>.
At runtime you can always use the management console (such as JConsole) to change on a given route or processor whether its statistics are enabled or not.
...
Statistics enabled means that Camel will do fine grained performance statistics for that particular MBean. The statistics you can see are many, such as: number of exchanges completed/failed, last/total/mina/max/mean processing time, first/last failed time, etc.
Using Java DSL you set this level by:
...
And from Spring DSL you do:
...
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 information can be hidden by enabling the mask option as shown below:
Using Java DSL you turn this on by:
...
...
And from Spring DSL you do:
...
...
This will mask URIs having options such as password and passphrase, and use xxxxxx as the replacement value.
Declaring which JMX attributes and operations to mask (hide sensitive information)
On the org.apache.camel.api.management.ManagedAttribute and org.apache.camel.api.management.ManagedOperation, the attribute mask 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 org.apache.camel.api.management.mbean.ManagedEndpointMBean, we have declared that the EndpointUri JMX attribute is masked.
...
...