Page History

id

The JMX agent name, and it is not optional

usePlatformMBeanServer

org.apache.camel.jmx.usePlatformMBeanServer

false, true - Release 1.5 or later

If true, it will use the MBeanServer from the JVM

mbeanServerDefaultDomain

org.apache.camel.jmx.mbeanServerDefaultDomain

org.apache.camel

The default JMX domain of the MBeanServer

mbeanObjectDomainName

org.apache.camel.jmx.mbeanObjectDomainName

org.apache.camel

The JMX domain that all object names will use

createConnector

org.apache.camel.jmx.createRmiConnect

false

If we should create a JMX connector (to allow remote management) for the MBeanServer

registryPort

org.apache.camel.jmx.rmiConnector.registryPort

1099

The port that the JMX RMI registry will use

connectorPort

org.apache.camel.jmx.rmiConnector.connectorPort

-1 (dynamic)

The port that the JMX RMI server will use

serviceUrlPath

org.apache.camel.jmx.serviceUrlPath

/jmxrmi/camel

The path that JMX connector will be registered under

onlyRegisterProcessorWithCustomId

org.apache.camel.jmx.onlyRegisterProcessorWithCustomId

false

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.

statisticsLevel

All / Default

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 onwards the All option is renamed to Default, and a new Extended option has been introduced which allows gathered additional runtime JMX metrics.

includeHostName

org.apache.camel.jmx.includeHostName

Camel 2.13: Whether to include the hostname in the MBean naming. From Camel 2.13 onwards this is default false, where as in older releases its default true. You can use this option to restore old behavior if really needed.