Author: buildbot
Date: Tue Aug 6 12:21:13 2013
New Revision: 873171
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/camel-jmx.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/camel-jmx.html
==============================================================================
--- websites/production/camel/content/camel-jmx.html (original)
+++ websites/production/camel/content/camel-jmx.html Tue Aug 6 12:21:13 2013
@@ -93,7 +93,7 @@ Camel also provides a <a shape="rect" hr
<h3><a shape="rect" name="CamelJMX-ActivatingJMXinCamel"></a>Activating JMX in
Camel</h3>
<div>
-<ul><li><a shape="rect" href="#CamelJMX-CamelJMX">Camel JMX</a></li><ul><li><a
shape="rect" href="#CamelJMX-ActivatingJMXinCamel">Activating JMX in
Camel</a></li><ul><li><a shape="rect"
href="#CamelJMX-UsingJMXtomanageApacheCamel">Using JMX to manage Apache
Camel</a></li><li><a shape="rect"
href="#CamelJMX-DisablingJMXinstrumentationagentinCamel">Disabling JMX
instrumentation agent in Camel</a></li><li><a shape="rect"
href="#CamelJMX-LocatingaMBeanServerintheJavaVM">Locating a MBeanServer in the
Java VM</a></li><li><a shape="rect"
href="#CamelJMX-CreatingJMXRMIConnectorServer">Creating JMX RMI Connector
Server</a></li><li><a shape="rect" href="#CamelJMX-JMXServiceURL">JMX Service
URL</a></li><li><a shape="rect"
href="#CamelJMX-TheSystemPropertiesforCamelJMXsupport">The SystemProperties for
Camel JMX support</a></li><li><a shape="rect"
href="#CamelJMX-HowtouseauthenticationwithJMX">How to use authentication with
JMX</a></li><li><a shape="rect" href="#CamelJMX-JMXinsideanApplicationSe
rver">JMX inside an Application Server</a></li><ul><li><a shape="rect"
href="#CamelJMX-Tomcat6">Tomcat 6</a></li><li><a shape="rect"
href="#CamelJMX-JBossAS4">JBoss AS 4</a></li><li><a shape="rect"
href="#CamelJMX-WebSphere">WebSphere</a></li><li><a shape="rect"
href="#CamelJMX-OracleOC4j">Oracle OC4j</a></li></ul><li><a shape="rect"
href="#CamelJMX-AdvancedJMXConfiguration">Advanced JMX
Configuration</a></li><li><a shape="rect"
href="#CamelJMX-Example%3A">Example:</a></li><li><a shape="rect"
href="#CamelJMX-jmxAgentPropertiesReference">jmxAgent Properties
Reference</a></li><li><a shape="rect"
href="#CamelJMX-Configuringwhethertoregistermbeansalways%2Cfornewroutesorjustbydefault">Configuring
whether to register mbeans always, for new routes or just by
default</a></li></ul><li><a shape="rect"
href="#CamelJMX-MonitoringCamelusingJMX">Monitoring Camel using
JMX</a></li><ul><li><a shape="rect"
href="#CamelJMX-UsingJConsoletomonitorCamel">Using JConsole to monitor
Camel</a></li><li><a sh
ape="rect" href="#CamelJMX-Whichendpointsareregistered">Which endpoints are
registered</a></li><li><a shape="rect"
href="#CamelJMX-Whichprocessorsareregistered">Which processors are
registered</a></li><li><a shape="rect"
href="#CamelJMX-HowtousetheJMXNotificationListenertolistenthecamelevents%3F">How
to use the JMX NotificationListener to listen the camel events?</a></li><li><a
shape="rect" href="#CamelJMX-UsingtheTracermbeantogetfinegrainedtracing">Using
the Tracer mbean to get fine grained tracing</a></li></ul><li><a shape="rect"
href="#CamelJMX-UsingJMXforyourownCamelCode">Using JMX for your own Camel
Code</a></li><ul><li><a shape="rect"
href="#CamelJMX-RegisteringyourownManagedEndpoints">Registering your own
Managed Endpoints</a></li><li><a shape="rect"
href="#CamelJMX-ProgrammingyourownManagedServices">Programming your own Managed
Services</a></li><li><a shape="rect"
href="#CamelJMX-ManagementNamingStrategy">ManagementNamingStrategy</a></li><li><a
shape="rect" href="#CamelJMX-M
anagementnamingpattern">Management naming pattern</a></li><li><a shape="rect"
href="#CamelJMX-ManagementStrategy">ManagementStrategy</a></li><li><a
shape="rect"
href="#CamelJMX-Configuringlevelofgranularityforperformancestatistics">Configuring
level of granularity for performance statistics</a></li></ul><li><a
shape="rect" href="#CamelJMX-Hidingsensitiveinformation">Hiding sensitive
information</a></li><ul><li><a shape="rect"
href="#CamelJMX-DeclaringwhichJMXattributesandoperationstosanitize%28hidesensitiveinformation%29">Declaring
which JMX attributes and operations to sanitize (hide sensitive
information)</a></li></ul><li><a shape="rect" href="#CamelJMX-SeeAlso">See
Also</a></li></ul></ul></div>
+<ul><li><a shape="rect" href="#CamelJMX-CamelJMX">Camel JMX</a></li><ul><li><a
shape="rect" href="#CamelJMX-ActivatingJMXinCamel">Activating JMX in
Camel</a></li><ul><li><a shape="rect"
href="#CamelJMX-UsingJMXtomanageApacheCamel">Using JMX to manage Apache
Camel</a></li><li><a shape="rect"
href="#CamelJMX-DisablingJMXinstrumentationagentinCamel">Disabling JMX
instrumentation agent in Camel</a></li><li><a shape="rect"
href="#CamelJMX-LocatingaMBeanServerintheJavaVM">Locating a MBeanServer in the
Java VM</a></li><li><a shape="rect"
href="#CamelJMX-CreatingJMXRMIConnectorServer">Creating JMX RMI Connector
Server</a></li><li><a shape="rect" href="#CamelJMX-JMXServiceURL">JMX Service
URL</a></li><li><a shape="rect"
href="#CamelJMX-TheSystemPropertiesforCamelJMXsupport">The System Properties
for Camel JMX support</a></li><li><a shape="rect"
href="#CamelJMX-HowtouseauthenticationwithJMX">How to use authentication with
JMX</a></li><li><a shape="rect" href="#CamelJMX-JMXinsideanApplicationS
erver">JMX inside an Application Server</a></li><ul><li><a shape="rect"
href="#CamelJMX-Tomcat6">Tomcat 6</a></li><li><a shape="rect"
href="#CamelJMX-JBossAS4">JBoss AS 4</a></li><li><a shape="rect"
href="#CamelJMX-WebSphere">WebSphere</a></li><li><a shape="rect"
href="#CamelJMX-OracleOC4j">Oracle OC4j</a></li></ul><li><a shape="rect"
href="#CamelJMX-AdvancedJMXConfiguration">Advanced JMX
Configuration</a></li><li><a shape="rect"
href="#CamelJMX-Example%3A">Example:</a></li><li><a shape="rect"
href="#CamelJMX-jmxAgentPropertiesReference">jmxAgent Properties
Reference</a></li><li><a shape="rect"
href="#CamelJMX-ConfiguringwhethertoregisterMBeansalways%2Cfornewroutesorjustbydefault">Configuring
whether to register MBeans always, for new routes or just by
default</a></li></ul><li><a shape="rect"
href="#CamelJMX-MonitoringCamelusingJMX">Monitoring Camel using
JMX</a></li><ul><li><a shape="rect"
href="#CamelJMX-UsingJConsoletomonitorCamel">Using JConsole to monitor
Camel</a></li><li><a s
hape="rect" href="#CamelJMX-Whichendpointsareregistered">Which endpoints are
registered</a></li><li><a shape="rect"
href="#CamelJMX-Whichprocessorsareregistered">Which processors are
registered</a></li><li><a shape="rect"
href="#CamelJMX-HowtousetheJMXNotificationListenertolistenthecamelevents%3F">How
to use the JMX NotificationListener to listen the camel events?</a></li><li><a
shape="rect" href="#CamelJMX-UsingtheTracerMBeantogetfinegrainedtracing">Using
the Tracer MBean to get fine grained tracing</a></li></ul><li><a shape="rect"
href="#CamelJMX-UsingJMXforyourownCamelCode">Using JMX for your own Camel
Code</a></li><ul><li><a shape="rect"
href="#CamelJMX-RegisteringyourownManagedEndpoints">Registering your own
Managed Endpoints</a></li><li><a shape="rect"
href="#CamelJMX-ProgrammingyourownManagedServices">Programming your own Managed
Services</a></li><li><a shape="rect"
href="#CamelJMX-ManagementNamingStrategy">ManagementNamingStrategy</a></li><li><a
shape="rect" href="#CamelJMX-
Managementnamingpattern">Management naming pattern</a></li><li><a shape="rect"
href="#CamelJMX-ManagementStrategy">ManagementStrategy</a></li><li><a
shape="rect"
href="#CamelJMX-Configuringlevelofgranularityforperformancestatistics">Configuring
level of granularity for performance statistics</a></li></ul><li><a
shape="rect" href="#CamelJMX-Hidingsensitiveinformation">Hiding sensitive
information</a></li><ul><li><a shape="rect"
href="#CamelJMX-DeclaringwhichJMXattributesandoperationstosanitize%28hidesensitiveinformation%29">Declaring
which JMX attributes and operations to sanitize (hide sensitive
information)</a></li></ul><li><a shape="rect" href="#CamelJMX-SeeAlso">See
Also</a></li></ul></ul></div>
<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1"><b>Spring JAR dependency, required for Camel 2.8 or older</b><br
clear="none"><tt>spring-context.jar</tt>, <tt>spring-aop.jar</tt>,
<tt>spring-beans.jar</tt>, and <tt>spring-core.jar</tt> are needed on the
classpath by Camel to be able to use JMX instrumentation. If these .jars are
not on the classpath, Camel will fallback to non JMX mode. This situation is
logged at <tt>WARN</tt> level using logger name
<tt>org.apache.camel.impl.DefaultCamelContext</tt>.
@@ -101,7 +101,7 @@ Camel also provides a <a shape="rect" hr
<h4><a shape="rect" name="CamelJMX-UsingJMXtomanageApacheCamel"></a>Using JMX
to manage Apache Camel</h4>
-<p>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.</p>
+<p>By default, JMX instrumentation agent is enabled in Camel, which means that
Camel runtime creates and registers MBean management objects with a
<tt>MBeanServer</tt> instance in the VM. This allows Camel users to instantly
obtain insights into how Camel routes perform down to the individual processor
level.</p>
<p>The supported types of management objects are <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/management/mbean/ManagedEndpoint.html";>endpoint</a>,
<a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/management/mbean/ManagedRoute.html";>route</a>,
<a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/management/mbean/ManagedService.html";>service</a>,
and <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/management/mbean/ManagedProcessor.html";>processor</a>.
Some of these management objects also expose lifecycle operations in addition
to performance counter attributes.</p>
@@ -150,7 +150,7 @@ camel.disableJMX();
<h4><a shape="rect"
name="CamelJMX-LocatingaMBeanServerintheJavaVM"></a>Locating a MBeanServer in
the Java VM</h4>
-<p>Each CamelContext can have an instance of <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/spi/InstrumentationAgent.html";>InstrumentationAgent</a>
wrapped inside the <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/management/InstrumentationLifecycleStrategy.html";>InstrumentationLifecycleStrategy</a>.
The InstrumentationAgent is the object that interfaces with a <a shape="rect"
class="external-link"
href="http://java.sun.com/j2se/1.5.0/docs/api/javax/management/MBeanServer.html";
rel="nofollow">MBeanServer</a> to register/unregister Camel MBeans. Multiple
CamelContexts/InstrumentationAgents can/should share a MBeanServer. By default,
Camel runtime picks the first MBeanServer returned by <a shape="rect"
class="external-link"
href="http://java.sun.com/j2se/1.5.0/docs/api/javax/management/MBeanServerFactory.html#findMBeanServer(java.lang.String)"
r
el="nofollow">MBeanServerFactory.findMBeanServer method</a> that matches the
default domain name of <b>org.apache.camel</b>. 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.</p>
+<p>Each CamelContext can have an instance of <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/spi/InstrumentationAgent.html";>InstrumentationAgent</a>
wrapped inside the <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/management/InstrumentationLifecycleStrategy.html";>InstrumentationLifecycleStrategy</a>.
The InstrumentationAgent is the object that interfaces with a <a shape="rect"
class="external-link"
href="http://java.sun.com/j2se/1.5.0/docs/api/javax/management/MBeanServer.html";
rel="nofollow">MBeanServer</a> to register/unregister Camel MBeans. Multiple
CamelContexts/InstrumentationAgents can/should share a <tt>MBeanServer</tt>. By
default, Camel runtime picks the first <tt>MBeanServer</tt> returned by <a
shape="rect" class="external-link"
href="http://java.sun.com/j2se/1.5.0/docs/api/javax/management/MBeanServerFactory.html#findMBeanServer(ja
va.lang.String)" rel="nofollow">MBeanServerFactory.findMBeanServer method</a>
that matches the default domain name of <b>org.apache.camel</b>. You may want
to change the default domain name to match the <tt>MBeanServer</tt> instance
that you are already using in your application. Especially, if your
<tt>MBeanServer</tt> is attached to a JMX connector server, you will not need
to create a connector server in Camel.</p>
<p>You can configure the matching default domain name via system property.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
@@ -167,9 +167,9 @@ camel.disableJMX();
</camelContext>
]]></script>
</div></div>
-<p>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.</p>
+<p>If no matching <tt>MBeanServer</tt> can be found, a new one is created and
the new <tt>MBeanServer</tt>'s default domain name is set according to the
default and configuration as mentioned above.</p>
-<p>It is also possible to use the <a shape="rect" class="external-link"
href="http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/ManagementFactory.html#getPlatformMBeanServer()"
rel="nofollow">PlatformMBeanServer</a> 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. <b>Starting in next release
(1.5), the default value of <tt>usePlatformMBeanServer</tt> will be changed to
"True". You can set the property to "False" to disable using platform MBean
server.</b></p>
+<p>It is also possible to use the <a shape="rect" class="external-link"
href="http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/ManagementFactory.html#getPlatformMBeanServer()"
rel="nofollow">PlatformMBeanServer</a> when it is desirable to manage JVM
MBeans by setting the system property. The <tt>MBeanServer</tt> default domain
name configuration is ignored as it is not applicable. <b>Starting in next
release (1.5), the default value of <tt>usePlatformMBeanServer</tt> will be
changed to "True". You can set the property to "False" to disable using
platform <tt>MBeanServer</tt>.</b></p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-Dorg.apache.camel.jmx.usePlatformMBeanServer=True
@@ -187,7 +187,7 @@ camel.disableJMX();
<h4><a shape="rect" name="CamelJMX-CreatingJMXRMIConnectorServer"></a>Creating
JMX RMI Connector Server</h4>
-<p>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.</p>
+<p>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 <tt>MBeanServer</tt> used by Camel is attached
to that connector server.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-Dorg.apache.camel.jmx.createRmiConnector=True
@@ -277,7 +277,7 @@ service:jmx:rmi://localhost:<connecto
]]></script>
</div></div>
-<h4><a shape="rect"
name="CamelJMX-TheSystemPropertiesforCamelJMXsupport"></a>The SystemProperties
for Camel JMX support</h4>
+<h4><a shape="rect"
name="CamelJMX-TheSystemPropertiesforCamelJMXsupport"></a>The System Properties
for Camel JMX support</h4>
<div class="table-wrap">
<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Property Name </th><th colspan="1" rowspan="1"
class="confluenceTh"> value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> org.apache.camel.jmx </td><td colspan="1" rowspan="1"
class="confluenceTd"> true or false </td><td colspan="1" rowspan="1"
class="confluenceTd"> if is true , it will enable jmx feature in Camel
</td></tr></tbody></table>
@@ -311,9 +311,9 @@ service:jmx:rmi://localhost:<connecto
<h5><a shape="rect" name="CamelJMX-JBossAS4"></a>JBoss AS 4</h5>
-<p>By default JBoss creates its own MBean server. To allow Camel to expose to
the same server follow these steps:</p>
+<p>By default JBoss creates its own <tt>MBeanServer</tt>. To allow Camel to
expose to the same server follow these steps:</p>
-<p>1. Tell Camel to use the Platform MBean Server (This defaults to true in
Camel 1.5)</p>
+<p>1. Tell Camel to use the Platform <tt>MBeanServer</tt> (This defaults to
true in Camel 1.5)</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
<camel:camelContext id="camelContext">
@@ -322,12 +322,12 @@ service:jmx:rmi://localhost:<connecto
]]></script>
</div></div>
-<p>2. Alter your JBoss instance to use the Platform MBean server.<br
clear="none">
+<p>2. Alter your JBoss instance to use the Platform <tt>MBeanServer</tt>.<br
clear="none">
Add the following property to your JAVA_OPTS by editing run.sh or run.conf {{
-Djboss.platform.mbeanserver }} See <a shape="rect" class="external-link"
href="http://wiki.jboss.org/wiki/JBossMBeansInJConsole";
rel="nofollow">http://wiki.jboss.org/wiki/JBossMBeansInJConsole</a></p>
<h5><a shape="rect" name="CamelJMX-WebSphere"></a>WebSphere</h5>
-<p>Alter the mbeanServerDefaultDomain to be "WebSphere"</p>
+<p>Alter the <tt>mbeanServerDefaultDomain</tt> to be "WebSphere"</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
@@ -337,7 +337,7 @@ Add the following property to your JAVA_
<h5><a shape="rect" name="CamelJMX-OracleOC4j"></a>Oracle OC4j</h5>
-<p>The Oracle OC4J J2EE application server will not allow Camel to access the
platform mbean server. You can identify this in the log as Camel will log a
WARNING.</p>
+<p>The Oracle OC4J J2EE application server will not allow Camel to access the
platform <tt>MBeanServer</tt>. You can identify this in the log as Camel will
log a <tt>WARNING</tt>.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
xxx xx, xxxx xx:xx:xx xx
org.apache.camel.management.InstrumentationLifecycleStrategy onContextStart
@@ -350,7 +350,7 @@ java.lang.SecurityException: Unauthorize
<h4><a shape="rect" name="CamelJMX-AdvancedJMXConfiguration"></a>Advanced JMX
Configuration</h4>
-<p>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.</p>
+<p>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.</p>
<h4><a shape="rect" name="CamelJMX-Example%3A"></a>Example:</h4>
@@ -379,33 +379,33 @@ SUNJMX=-Dcom.sun.management.jmxremote=tr
<h4><a shape="rect" name="CamelJMX-jmxAgentPropertiesReference"></a>jmxAgent
Properties Reference</h4>
<div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Spring property </th><th colspan="1" rowspan="1"
class="confluenceTh"> System property </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> id </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> The JMX agent name, and it is not optional
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
usePlatformMBeanServer </td><td colspan="1" rowspan="1" class="confluenceTd">
org.apache.camel.jmx.usePlatformMBeanServer </td><td colspan="1" rowspan="1"
class="confluenceTd"> false, true - Release 1.5 or later </td><td colspan="1"
rowspan="1" class="confluenceTd"> If true, it will use the MBean server from
the JVM </td></tr><tr><
td colspan="1" rowspan="1" class="confluenceTd"> mbeanServerDefaultDomain
</td><td colspan="1" rowspan="1" class="confluenceTd">
org.apache.camel.jmx.mbeanServerDefaultDomain </td><td colspan="1" rowspan="1"
class="confluenceTd"> org.apache.camel </td><td colspan="1" rowspan="1"
class="confluenceTd"> The default JMX domain of the MBeanServer
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
mbeanObjectDomainName </td><td colspan="1" rowspan="1" class="confluenceTd">
org.apache.camel.jmx.mbeanObjectDomainName </td><td colspan="1" rowspan="1"
class="confluenceTd"> org.apache.camel </td><td colspan="1" rowspan="1"
class="confluenceTd"> The JMX domain that all object names will use
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> createConnector
</td><td colspan="1" rowspan="1" class="confluenceTd">
org.apache.camel.jmx.createRmiConnect </td><td colspan="1" rowspan="1"
class="confluenceTd"> false </td><td colspan="1" rowspan="1"
class="confluenceTd"> If we s
hould create a JMX connector (to allow remote management) for the MBeanServer
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> registryPort
</td><td colspan="1" rowspan="1" class="confluenceTd">
org.apache.camel.jmx.rmiConnector.registryPort </td><td colspan="1" rowspan="1"
class="confluenceTd"> 1099 </td><td colspan="1" rowspan="1"
class="confluenceTd"> The port that the JMX RMI registry will use
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> connectorPort
</td><td colspan="1" rowspan="1" class="confluenceTd">
org.apache.camel.jmx.rmiConnector.connectorPort </td><td colspan="1"
rowspan="1" class="confluenceTd"> -1 (dynamic) </td><td colspan="1" rowspan="1"
class="confluenceTd"> The port that the JMX RMI server will use
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> serviceUrlPath
</td><td colspan="1" rowspan="1" class="confluenceTd">
org.apache.camel.jmx.serviceUrlPath </td><td colspan="1" rowspan="1"
class="confluenceTd"> /jmxrmi/ca
mel </td><td colspan="1" rowspan="1" class="confluenceTd"> The path that JMX
connector will be registered under </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> onlyRegisterProcessorWithCustomId </td><td colspan="1"
rowspan="1" class="confluenceTd">
org.apache.camel.jmx.onlyRegisterProcessorWithCustomId </td><td colspan="1"
rowspan="1" class="confluenceTd"> false </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.0:</b> 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. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> statisticsLevel </td><td colspan="1"
rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>All</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.1:</b> Configures the level for whether
performance statistics is enabled for the mbean. See section <em>Configu
ring level of granularity for performance statistics</em> for more details.
</td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Spring property </th><th colspan="1" rowspan="1"
class="confluenceTh"> System property </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>id</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> The JMX agent name, and it is not optional
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>usePlatformMBeanServer</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>org.apache.camel.jmx.usePlatformMBeanServer</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt>,
<tt>true</tt> - Release 1.5 or later </td><td colspan="1" rowspan="1"
class="confluenceTd"> If <tt>true</tt>, it
will use the <tt>MBeanServer</tt> from the JVM </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>mbeanServerDefaultDomain</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd">
<tt>org.apache.camel.jmx.mbeanServerDefaultDomain</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>org.apache.camel</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> The default JMX domain of the
<tt>MBeanServer</tt> </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>mbeanObjectDomainName</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd">
<tt>org.apache.camel.jmx.mbeanObjectDomainName</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>org.apache.camel</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> The JMX domain that all object
names will use </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>createConnector</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>org.apache.camel.jmx.cr
eateRmiConnect</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If we
should create a JMX connector (to allow remote management) for the
<tt>MBeanServer</tt> </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>registryPort</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>org.apache.camel.jmx.rmiConnector.registryPort</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1099</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> The port that the JMX RMI
registry will use </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>connectorPort</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>org.apache.camel.jmx.rmiConnector.connectorPort</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> -1 (dynamic) </td><td
colspan="1" rowspan="1" class="confluenceTd"> The port that the JMX RMI server
will use </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>serviceUrlPath</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd">
<tt>org.apache.camel.jmx.serviceUrlPath</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>/jmxrmi/camel</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> The path that JMX connector will be registered under
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>onlyRegisterProcessorWithCustomId</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd">
<tt>org.apache.camel.jmx.onlyRegisterProcessorWithCustomId</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.0:</b> 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.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>statisticsLevel</tt> </td><td colspan="1" rowspan="1" clas
s="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>All</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel
2.1:</b> Configures the level for whether performance statistics is enabled for
the MBean. See section <em>Configuring level of granularity for performance
statistics</em> for more details. </td></tr></tbody></table>
</div>
-<h4><a shape="rect"
name="CamelJMX-Configuringwhethertoregistermbeansalways%2Cfornewroutesorjustbydefault"></a>Configuring
whether to register mbeans always, for new routes or just by default</h4>
+<h4><a shape="rect"
name="CamelJMX-ConfiguringwhethertoregisterMBeansalways%2Cfornewroutesorjustbydefault"></a>Configuring
whether to register MBeans always, for new routes or just by default</h4>
<p><b>Available as of Camel 2.7</b></p>
<p>Camel now offers 2 settings to control whether or not to register mbeans</p>
<div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> registerAlways </td><td colspan="1" rowspan="1"
class="confluenceTd"> false </td><td colspan="1" rowspan="1"
class="confluenceTd"> If enabled then mbeans is always registered.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
registerNewRoutes </td><td colspan="1" rowspan="1" class="confluenceTd"> true
</td><td colspan="1" rowspan="1" class="confluenceTd"> If enabled then adding
new routes after <a shape="rect" href="camelcontext.html"
title="CamelContext">CamelContext</a> has been started will also register
mbeans from that given route. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>registerAlways</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> If enabled then MBeans is always registered.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>registerNewRoutes</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> If enabled then adding new routes after <a shape="rect"
href="camelcontext.html" title="CamelContext">CamelContext</a> has been started
will also register MBeans from that given route. </td></tr></tbody></table>
</div>
-<p>By default Camel registers mbeans for all the routes configured when its
starting. The <tt>registerNewRoutes</tt> 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.</p>
+<p>By default Camel registers MBeans for all the routes configured when its
starting. The <tt>registerNewRoutes</tt> 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.</p>
-<p>Be a bit caution to use the registerAlways option when using dynamic <a
shape="rect" href="eip.html" title="EIP">EIP</a> patterns such as the <a
shape="rect" href="recipient-list.html" title="Recipient List">Recipient
List</a> having unique endpoints. If so then each unique endpoint and its
associated services/producers would also be registered. This could potential
lead to system degration due the rising number of mbeans in the registry. A
MBean is not a light-weight object and thus consume memory.</p>
+<p>Be a bit caution to use the <tt>registerAlways</tt> option when using
dynamic <a shape="rect" href="eip.html" title="EIP">EIP</a> patterns such as
the <a shape="rect" href="recipient-list.html" title="Recipient List">Recipient
List</a> having unique endpoints. If so then each unique endpoint and its
associated services/producers would also be registered. This could potential
lead to system degration due the rising number of mbeans in the registry. A
MBean is not a light-weight object and thus consumes memory.</p>
<h3><a shape="rect" name="CamelJMX-MonitoringCamelusingJMX"></a>Monitoring
Camel using JMX</h3>
<h4><a shape="rect" name="CamelJMX-UsingJConsoletomonitorCamel"></a>Using
JConsole to monitor Camel</h4>
-<p>The CamelContext should appear in the list of local connections, if you are
running JConsole on the same host as Camel.</p>
+<p>The <tt>CamelContext</tt> should appear in the list of local connections,
if you are running JConsole on the same host as Camel.</p>
<p>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</p>
-<p>Using the Apache Camel which Jconsole</p>
+<p>Using the Apache Camel with JConsole</p>
<p><span class="image-wrap" style=""><img src="camel-jmx.data/camel-jmx.png"
style="border: 1px solid black"></span></p>
@@ -461,13 +461,13 @@ context.getManagementStrategy().getManag
]]></script>
</div></div>
-<h4><a shape="rect"
name="CamelJMX-UsingtheTracermbeantogetfinegrainedtracing"></a>Using the Tracer
mbean to get fine grained tracing</h4>
+<h4><a shape="rect"
name="CamelJMX-UsingtheTracerMBeantogetfinegrainedtracing"></a>Using the Tracer
MBean to get fine grained tracing</h4>
<p>Additionally to the coarse grained notifications above <b>Camel 2.9.0</b>
support JMX Notification for fine grained trace events.<br clear="none">
-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.<br clear="none">
-This can either be done when configuring the context or on the context / route
mbeans.</p>
+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.<br clear="none">
+This can either be done when configuring the context or on the context / route
MBeans.</p>
-<p>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 on the tracer mbean.</p>
+<p>As a second step you have to set the <tt>jmxTraceNotifications</tt>
attribute to <tt>true</tt> on the tracer. This can again be done when
configuring the context or at runtime on the tracer MBean.</p>
<p>Now you can register 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.</p>
@@ -478,7 +478,7 @@ This can either be done when configuring
<h4><a shape="rect"
name="CamelJMX-RegisteringyourownManagedEndpoints"></a>Registering your own
Managed Endpoints</h4>
<p><b>Available as of Camel 2.0</b><br clear="none">
-You can decorate your own endpoints with spring managed annotations
<tt>@ManagedResource</tt> to allow to register them in the Camel mbean server
and thus access your custom mbeans using JMX.<br clear="none">
+You can decorate your own endpoints with Spring managed annotations
<tt>@ManagedResource</tt> to allow to register them in the Camel
<tt>MBeanServer</tt> and thus access your custom MBeans using JMX.<br
clear="none">
<b>Notice:</b> in <b>Camel 2.1</b> we have changed this to apply other than
just endpoints but then you need to implement the interface
<tt>org.apache.camel.spi.ManagementAware</tt> as well. More about this
later.</p>
<p>For example we have the following custom endpoint where we define some
options to be managed:</p>
@@ -522,7 +522,7 @@ public class CustomEndpoint extends Mock
<p><b>Available as of Camel 2.1</b></p>
-<p>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
<tt>org.apache.camel.spi.ManagementAware</tt> and return the managed object
Camel should use.</p>
+<p>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
<tt>org.apache.camel.spi.ManagementAware</tt> and return the managed object
Camel should use.</p>
<p>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 <tt>this</tt> in the
<tt>getManagedObject</tt> from the <tt>ManagementAware</tt> interface. For an
example see the code example above with the <tt>CustomEndpoint</tt>.</p>
@@ -548,14 +548,14 @@ public class CustomEndpoint extends Mock
<p><b>Available as of Camel 2.1</b></p>
-<p>Camel provides a pluggable API for naming strategy by
<tt>org.apache.camel.spi.ManagementNamingStrategy</tt>. A default
implementation is used to compute the mbean names that all mbeans are
registered with.</p>
+<p>Camel provides a pluggable API for naming strategy by
<tt>org.apache.camel.spi.ManagementNamingStrategy</tt>. A default
implementation is used to compute the MBean names that all MBeans are
registered with.</p>
<h4><a shape="rect" name="CamelJMX-Managementnamingpattern"></a>Management
naming pattern</h4>
<p><b>Available as of Camel 2.10</b></p>
-<p>From <b>Camel 2.10</b> onwards we made it easier to configure a naming
pattern for the mbeans. The pattern is used as part of the <tt>ObjectName</tt>
as they key after the domain name.</p>
+<p>From <b>Camel 2.10</b> onwards we made it easier to configure a naming
pattern for the MBeans. The pattern is used as part of the <tt>ObjectName</tt>
as they key after the domain name.</p>
-<p>By default Camel will use MBean names for the ManagedCamelContextMBean as
follows:</p>
+<p>By default Camel will use MBean names for the
<tt>ManagedCamelContextMBean</tt> as follows:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
org.apache.camel:context=localhost/camel-1,type=context,name=camel-1
@@ -575,7 +575,7 @@ org.apache.camel:context=localhost/myCam
]]></script>
</div></div>
-<p>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 <tt>ObjectName</tt>:</p>
+<p>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 <tt>JMXMBeanServer</tt> by using
a counter. As shown below the counter is now appended, so we have
<tt>myCamel-1</tt> as part of the <tt>ObjectName</tt>:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
org.apache.camel:context=localhost/myCamel-1,type=context,name=myCamel
@@ -590,14 +590,14 @@ org.apache.camel:context=localhost/myCam
<ul class="alternate" type="square"><li>non OSGI: #name#</li><li>OSGi:
#bundleId#-#name#</li></ul>
-<p>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:</p>
+<p>However if there is a naming clash in the <tt>JMXMBeanServer</tt> then
Camel will automatic fallback and use the #counter# in the pattern to remedy
this. And thus the following patterns will then be used:</p>
<ul class="alternate" type="square"><li>non OSGI:
#name#-#counter#</li><li>OSGi: #bundleId#-#name#-#counter#</li></ul>
<p>If you set an explicit naming pattern, then that pattern is always used,
and the default patterns above is <b>not</b> used.<br clear="none">
-This allows us to have full control, very easily, of the naming for both the
<tt>CamelContext</tt> id in the <a shape="rect" href="registry.html"
title="Registry">Registry</a> as well the JMX mbeans in the
JMXMBeanRegistry.</p>
+This allows us to have full control, very easily, of the naming for both the
<tt>CamelContext</tt> id in the <a shape="rect" href="registry.html"
title="Registry">Registry</a> as well the JMX MBeans in the
<tt>JMXMBeanRegistry</tt>.</p>
-<p>So if we want to explicit name both the <tt>CamelContext</tt> and to use
fixed mbean names, that do not change (eg has no counters), then we can use the
new <tt>managementNamePattern</tt> attribute:</p>
+<p>So if we want to explicit name both the <tt>CamelContext</tt> and to use
fixed MBean names, that do not change (eg has no counters), then we can use the
new <tt>managementNamePattern</tt> attribute:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
<camelContext id="myCamel" managementNamePattern="#name#">
@@ -624,7 +624,7 @@ context.getManagementNameStrategy().setN
]]></script>
</div></div>
-<p>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:</p>
+<p>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:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
<camelContext id="myCamel" managementNamePattern="#name#">
@@ -636,7 +636,7 @@ context.getManagementNameStrategy().setN
<p><b>Available as of Camel 2.1</b></p>
-<p>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 mbean
server, but also event notification is provided as well using the
<tt>org.apache.camel.spi.EventNotifier</tt> 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.</p>
+<p>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
<tt>MBeanServer</tt>, but also event notification is provided as well using the
<tt>org.apache.camel.spi.EventNotifier</tt> 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.</p>
<h4><a shape="rect"
name="CamelJMX-Configuringlevelofgranularityforperformancestatistics"></a>Configuring
level of granularity for performance statistics</h4>
@@ -646,11 +646,11 @@ context.getManagementNameStrategy().setN
<ul class="alternate" type="square"><li><tt>All</tt> <b>default</b> - Camel
will enable statistics for both routes and processors (fine
grained)</li><li><tt>RoutesOnly</tt> - Camel will only enable statistics for
routes (coarse grained)</li><li><tt>Off</tt> - Camel will not enable statistics
for any.</li></ul>
-<p>From <b>Camel 2.9</b> 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. <b>Camel
2.11</b> onwards allows you to explicit disable load performance statistics by
setting <tt>loadStatisticsEnabled=false</tt> on the <jmxAgent>. Note that
it will be off if the statics level is configured to off as well.</p>
+<p>From <b>Camel 2.9</b> 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. <b>Camel
2.11</b> onwards allows you to explicit disable load performance statistics by
setting <tt>loadStatisticsEnabled=false</tt> on the <jmxAgent>. Note that
it will be off if the statics level is configured to off as well.</p>
-<p>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.</p>
+<p>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.</p>
-<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1"><b>What does statistics enabled mean?</b><br
clear="none">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.</td></tr></table></div>
+<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1"><b>What does statistics enabled mean?</b><br
clear="none">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.</td></tr></table></div>
<p>Using Java DSL you set this level by:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
@@ -674,8 +674,8 @@ context.getManagementNameStrategy().setN
<h3><a shape="rect" name="CamelJMX-Hidingsensitiveinformation"></a>Hiding
sensitive information</h3>
<p><b>Available as of Camel 2.12</b></p>
-<p>By default Camel enlist MBeans in JMX such as endpoints configured using <a
shape="rect" href="uris.html" title="URIs">URIs</a>. In these configuration
there may be sensitive information such as passwords. <br clear="none">
-These information can be hidden by enabling the sanitize option as shown
below:</p>
+<p>By default, Camel enlists MBeans in JMX such as endpoints configured using
<a shape="rect" href="uris.html" title="URIs">URIs</a>. In this configuration,
there may be sensitive information such as passwords. <br clear="none">
+This information can be hidden by enabling the <tt>sanitize</tt> option as
shown below:</p>
<p>Using Java DSL you turn this on by:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
@@ -695,13 +695,13 @@ These information can be hidden by enabl
]]></script>
</div></div>
-<p>This will mask <span class="error">[URI]</span>s having options such as
password and passphrase, and use <tt>xxxxxx</tt> as the replacement value.</p>
+<p>This will mask <a shape="rect" href="uris.html" title="URIs">URIs</a>
having options such as password and passphrase, and use <tt>xxxxxx</tt> as the
replacement value.</p>
<h4><a shape="rect"
name="CamelJMX-DeclaringwhichJMXattributesandoperationstosanitize%28hidesensitiveinformation%29"></a>Declaring
which JMX attributes and operations to sanitize (hide sensitive
information)</h4>
-<p>On the <tt>org.apache.camel.api.management.ManagedAttribute</tt> and
<tt>org.apache.camel.api.management.ManagedOperation</tt> the attribute
<tt>sanitize</tt> can be set to <tt>true</tt> to indicate that the result of
this JMX attribute/operation should be sanitized (if enabled on JMX agent, see
above).</p>
+<p>On the <tt>org.apache.camel.api.management.ManagedAttribute</tt> and
<tt>org.apache.camel.api.management.ManagedOperation</tt>, the attribute
<tt>sanitize</tt> can be set to <tt>true</tt> to indicate that the result of
this JMX attribute/operation should be sanitized (if enabled on JMX agent, see
above).</p>
-<p>For example on the out of the box managed endpoints from camel-core
<tt>org.apache.camel.api.management.mbean.ManagedEndpointMBean</tt> we have
declared that the <tt>EndpointUri</tt> JMX attribute is sanitized.</p>
+<p>For example, on the default managed endpoints from camel-core
<tt>org.apache.camel.api.management.mbean.ManagedEndpointMBean</tt>, we have
declared that the <tt>EndpointUri</tt> JMX attribute is sanitized.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><
![https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"](https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"){kind=link}