You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by bu...@apache.org on 2013/07/24 13:21:14 UTC
svn commit: r870975 - in /websites/production/camel/content:
cache/main.pageCache camel-2120-release.html camel-jmx.html
Author: buildbot
Date: Wed Jul 24 11:21:14 2013
New Revision: 870975
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/camel-2120-release.html
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-2120-release.html
==============================================================================
--- websites/production/camel/content/camel-2120-release.html (original)
+++ websites/production/camel/content/camel-2120-release.html Wed Jul 24 11:21:14 2013
@@ -94,7 +94,7 @@
<p>Welcome to the 2.12.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)</p>
-<ul><li><a shape="rect" href="endpoint-annotations.html" title="Endpoint Annotations">Endpoint Annotations</a> along with automatically created HTML documentation for the endpoint parameters; this makes it easier for component developers to add a few refactoring-safe annotations to their Endpoint or Consumer implementations and, (along with javadoc comments on the field or setter method), get nice user documentation on how to use the endpoint for free.</li><li><a shape="rect" href="componentconfiguration.html" title="ComponentConfiguration">ComponentConfiguration</a> API provides a handy API for tools developers to introspect on a Component to find all the possible parameters, their types and any extra annotations (like Bean Validation Annotations) to be able to create/edit endpoints or URI strings so that tools can generate nicer UIs for configuring endpoints than just letting folks edit Strings.</li><li><a shape="rect" href="endpointcompleter.html" title="EndpointCompleter">Endpoi
ntCompleter</a> API provides a hook so that command line tools (like <a shape="rect" class="external-link" href="http://karaf.apache.org/manual/latest-2.3.x/users-guide/using-console.html">Karaf's shell</a>), IDEs and web tools can get (bash tab like) auto-completion on endpoint paths (such as file or directory names, message queue names, database table names) when creating or using new endpoints</li><li>Reduced stack-frames in use during routing, that also makes Camel's stack traces being logged much less verbose. This also allows people to easier debug the internals of Camel as less <tt>AsyncCallback</tt> callbacks are in use during routing.</li><li>Easy to use <a shape="rect" href="message-history.html" title="Message History">Message History</a> out of the box. And included message history as "route stack-trace" when exceptions logged by <a shape="rect" href="error-handler.html" title="Error Handler">Error Handler</a> to make it easier for end users to spot where the exception o
ccurred.</li><li><a shape="rect" href="spring-web-services.html" title="Spring Web Services">Spring Web Services</a> now supports setting/receiving SOAP headers more easily using a header on the Camel <a shape="rect" href="message.html" title="Message">Message</a>.</li><li>Evaluating <a shape="rect" href="groovy.html" title="Groovy">Groovy</a> expressions is faster as we cache the compiled scripts.</li><li>Added <tt>base64</tt> option to <a shape="rect" href="shiro-security.html" title="Shiro Security">Shiro Security</a> to allow transferring security token over <a shape="rect" href="jms.html" title="JMS">JMS</a> and other transports as base64 encoded representation.</li><li>Made it easier to use <a shape="rect" href="shiro-security.html" title="Shiro Security">Shiro Security</a> as the credentials can be provided in headers, when sending a message to a secured route.</li><li><a shape="rect" href="bindy.html" title="Bindy">Bindy</a> now supports enums.</li><li>Added new <a shape="re
ct" href="backlogdebugger.html" title="BacklogDebugger">BacklogDebugger</a> to perform live debugging of messages during routing. The <a shape="rect" href="backlogdebugger.html" title="BacklogDebugger">BacklogDebugger</a> has JMX API allows tooling to control the debugger.</li><li>While using the <a shape="rect" class="external-link" href="http://xircles.codehaus.org/projects/jackson" rel="nofollow">Jackson library</a> through the <a shape="rect" href="json.html" title="JSON">JSON</a> Dataformat there's now a <tt>jsonView</tt> attribute you could make use of directly inside the <a shape="rect" href="dsl.html" title="DSL">DSL</a> itself.</li><li><a shape="rect" href="smpp.html" title="SMPP">SMPP</a> now supports optional parameters in all commands where they are possible.</li><li><a shape="rect" href="jdbc.html" title="JDBC">JDBC</a> now supports named parameters.</li><li>Added timeout support for <a shape="rect" href="direct.html" title="Direct">Direct</a> producers to wait for cons
umer to become active.</li><li>Added <tt>stats</tt> action to <a shape="rect" href="controlbus.html" title="ControlBus">ControlBus</a> to easily get performance statics in a single XML message.</li><li>Added support for request timeout on <a shape="rect" href="netty.html" title="Netty">Netty</a> producer, and to configure logging level on <a shape="rect" href="netty.html" title="Netty">Netty</a> consumer to be less noisy for ChannelClosedException which can flood the logs when client disconnects abruptly.</li><li><a shape="rect" href="springbatch.html" title="SpringBatch">Spring Batch</a> component producer now returns the <tt>JobExecution</tt> instance as the output message. Users can use the <tt>JobExecution</tt> instance to perform some operations using the Spring Batch API directly.</li><li>Added support for NULL values in <a shape="rect" href="sql-component.html" title="SQL Component">SQL</a> with named parameters.</li><li>Optimized <a shape="rect" href="jetty.html" title="Jett
y">Jetty</a> streaming responses in non-chunked mode; and as well using buffer sizes based on <tt>HttpServletResponse.getBufferSize()</tt> instead of fixed size of 4kb.</li><li>Added <tt>greedy</tt> option to <a shape="rect" href="polling-consumer.html" title="Polling Consumer">scheduled polling consumer</a>.</li><li>Added support for accessing the length field on Java arrays in <a shape="rect" href="simple.html" title="Simple">Simple</a> language.</li><li>Added support for using JAXB annotations with Camel's Jackson <a shape="rect" href="json.html" title="JSON">JSON</a> component.</li><li>Added the ability for <a shape="rect" href="bindy.html" title="Bindy">Bindy</a> to skip content when parsing fixed-length records.</li><li><a shape="rect" href="mongodb.html" title="MongoDB">MongoDB</a> now supports aggregation queries.</li><li><a shape="rect" href="netty.html" title="Netty">Netty</a> allows to use shared Netty boss and worker thread pools.</li><li>The <a shape="rect" href="camel-
maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven Archetypes</a> for component and data format now packages as OSGi bundles out of the box.</li><li>Easier <a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a> configuration using <tt>StreamCachingStrategy</tt>. Also allows spool directory per <a shape="rect" href="camelcontext.html" title="CamelContext">CamelContext</a> instead of shared per JVM. And insight at runtime using JMX management. As well allowing to plugin 3rd party implementations.</li><li>Improved <a shape="rect" href="netty.html" title="Netty">Netty</a> to be able to join an UDP multicast group.</li><li>Using Camel <a shape="rect" href="spring.html" title="Spring">Spring</a> is now setting up Camel routes later in the process allow Spring to complete all of its dependency injection, before Camel <tt>RouteBuilder</tt> instances is configured. This allows to safely use Spring dependency injection in these <tt>RouteBuilder</tt
> classes.</li></ul>
+<ul><li><a shape="rect" href="endpoint-annotations.html" title="Endpoint Annotations">Endpoint Annotations</a> along with automatically created HTML documentation for the endpoint parameters; this makes it easier for component developers to add a few refactoring-safe annotations to their Endpoint or Consumer implementations and, (along with javadoc comments on the field or setter method), get nice user documentation on how to use the endpoint for free.</li><li><a shape="rect" href="componentconfiguration.html" title="ComponentConfiguration">ComponentConfiguration</a> API provides a handy API for tools developers to introspect on a Component to find all the possible parameters, their types and any extra annotations (like Bean Validation Annotations) to be able to create/edit endpoints or URI strings so that tools can generate nicer UIs for configuring endpoints than just letting folks edit Strings.</li><li><a shape="rect" href="endpointcompleter.html" title="EndpointCompleter">Endpoi
ntCompleter</a> API provides a hook so that command line tools (like <a shape="rect" class="external-link" href="http://karaf.apache.org/manual/latest-2.3.x/users-guide/using-console.html">Karaf's shell</a>), IDEs and web tools can get (bash tab like) auto-completion on endpoint paths (such as file or directory names, message queue names, database table names) when creating or using new endpoints</li><li>Reduced stack-frames in use during routing, that also makes Camel's stack traces being logged much less verbose. This also allows people to easier debug the internals of Camel as less <tt>AsyncCallback</tt> callbacks are in use during routing.</li><li>Easy to use <a shape="rect" href="message-history.html" title="Message History">Message History</a> out of the box. And included message history as "route stack-trace" when exceptions logged by <a shape="rect" href="error-handler.html" title="Error Handler">Error Handler</a> to make it easier for end users to spot where the exception o
ccurred.</li><li><a shape="rect" href="spring-web-services.html" title="Spring Web Services">Spring Web Services</a> now supports setting/receiving SOAP headers more easily using a header on the Camel <a shape="rect" href="message.html" title="Message">Message</a>.</li><li>Evaluating <a shape="rect" href="groovy.html" title="Groovy">Groovy</a> expressions is faster as we cache the compiled scripts.</li><li>Added <tt>base64</tt> option to <a shape="rect" href="shiro-security.html" title="Shiro Security">Shiro Security</a> to allow transferring security token over <a shape="rect" href="jms.html" title="JMS">JMS</a> and other transports as base64 encoded representation.</li><li>Made it easier to use <a shape="rect" href="shiro-security.html" title="Shiro Security">Shiro Security</a> as the credentials can be provided in headers, when sending a message to a secured route.</li><li><a shape="rect" href="bindy.html" title="Bindy">Bindy</a> now supports enums.</li><li>Added new <a shape="re
ct" href="backlogdebugger.html" title="BacklogDebugger">BacklogDebugger</a> to perform live debugging of messages during routing. The <a shape="rect" href="backlogdebugger.html" title="BacklogDebugger">BacklogDebugger</a> has JMX API allows tooling to control the debugger.</li><li>While using the <a shape="rect" class="external-link" href="http://xircles.codehaus.org/projects/jackson" rel="nofollow">Jackson library</a> through the <a shape="rect" href="json.html" title="JSON">JSON</a> Dataformat there's now a <tt>jsonView</tt> attribute you could make use of directly inside the <a shape="rect" href="dsl.html" title="DSL">DSL</a> itself.</li><li><a shape="rect" href="smpp.html" title="SMPP">SMPP</a> now supports optional parameters in all commands where they are possible.</li><li><a shape="rect" href="jdbc.html" title="JDBC">JDBC</a> now supports named parameters.</li><li>Added timeout support for <a shape="rect" href="direct.html" title="Direct">Direct</a> producers to wait for cons
umer to become active.</li><li>Added <tt>stats</tt> action to <a shape="rect" href="controlbus.html" title="ControlBus">ControlBus</a> to easily get performance statics in a single XML message.</li><li>Added support for request timeout on <a shape="rect" href="netty.html" title="Netty">Netty</a> producer, and to configure logging level on <a shape="rect" href="netty.html" title="Netty">Netty</a> consumer to be less noisy for ChannelClosedException which can flood the logs when client disconnects abruptly.</li><li><a shape="rect" href="springbatch.html" title="SpringBatch">Spring Batch</a> component producer now returns the <tt>JobExecution</tt> instance as the output message. Users can use the <tt>JobExecution</tt> instance to perform some operations using the Spring Batch API directly.</li><li>Added support for NULL values in <a shape="rect" href="sql-component.html" title="SQL Component">SQL</a> with named parameters.</li><li>Optimized <a shape="rect" href="jetty.html" title="Jett
y">Jetty</a> streaming responses in non-chunked mode; and as well using buffer sizes based on <tt>HttpServletResponse.getBufferSize()</tt> instead of fixed size of 4kb.</li><li>Added <tt>greedy</tt> option to <a shape="rect" href="polling-consumer.html" title="Polling Consumer">scheduled polling consumer</a>.</li><li>Added support for accessing the length field on Java arrays in <a shape="rect" href="simple.html" title="Simple">Simple</a> language.</li><li>Added support for using JAXB annotations with Camel's Jackson <a shape="rect" href="json.html" title="JSON">JSON</a> component.</li><li>Added the ability for <a shape="rect" href="bindy.html" title="Bindy">Bindy</a> to skip content when parsing fixed-length records.</li><li><a shape="rect" href="mongodb.html" title="MongoDB">MongoDB</a> now supports aggregation queries.</li><li><a shape="rect" href="netty.html" title="Netty">Netty</a> allows to use shared Netty boss and worker thread pools.</li><li>The <a shape="rect" href="camel-
maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven Archetypes</a> for component and data format now packages as OSGi bundles out of the box.</li><li>Easier <a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a> configuration using <tt>StreamCachingStrategy</tt>. Also allows spool directory per <a shape="rect" href="camelcontext.html" title="CamelContext">CamelContext</a> instead of shared per JVM. And insight at runtime using JMX management. As well allowing to plugin 3rd party implementations.</li><li>Improved <a shape="rect" href="netty.html" title="Netty">Netty</a> to be able to join an UDP multicast group.</li><li>Using Camel <a shape="rect" href="spring.html" title="Spring">Spring</a> is now setting up Camel routes later in the process allow Spring to complete all of its dependency injection, before Camel <tt>RouteBuilder</tt> instances is configured. This allows to safely use Spring dependency injection in these <tt>RouteBuilder</tt
> classes.</li><li>Services in a <a shape="rect" href="camelcontext.html" title="CamelContext">CamelContext</a> which can only be enlisted once (eg it similar to a static in a JVM) has simpler and fixed MBean names in JMX.</li></ul>
<h3><a shape="rect" name="Camel2.12.0Release-FixedIssues"></a>Fixed Issues</h3>
Modified: websites/production/camel/content/camel-jmx.html
==============================================================================
--- websites/production/camel/content/camel-jmx.html (original)
+++ websites/production/camel/content/camel-jmx.html Wed Jul 24 11:21:14 2013
@@ -103,7 +103,7 @@ Camel also provides a <a shape="rect" hr
<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 instantly obtain insights into how Camel routes perform down to the individual processor's 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/ManagedEndpoint.html">endpoint </a>, <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/management/ManagedRoute.html">route</a>, <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/management/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/PerformanceCounter.html">processor</a>. Some of these management objects also expose lifecycle operations in addition to performance counter attributes.</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/ManagedEndpoint.html">endpoint</a>, <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/management/ManagedRoute.html">route</a>, <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/management/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/PerformanceCounter.html">processor</a>. Some of these management objects also expose lifecycle operations in addition to performance counter attributes.</p>
<p>The <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/management/DefaultManagementNamingStrategy.html">DefaultManagementNamingStrategy</a> is the default naming strategy which builds object names used for MBean registration. By default, <b>org.apache.camel</b> 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:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
@@ -140,7 +140,7 @@ Camel also provides a <a shape="rect" hr
]]></script>
</div></div>
-<p>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:</p>
+<p>Or in <b>Camel 2.1</b> its a bit easier (not having to use JVM system property) if using pure Java as you can disable it 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[
CamelContext camel = new DefaultCamelContext();
@@ -286,14 +286,12 @@ service:jmx:rmi://localhost:<connecto
<p>See more system properties in this section below: <em>jmxAgent Properties Reference</em></p>
-
<h4><a shape="rect" name="CamelJMX-HowtouseauthenticationwithJMX"></a>How to use authentication with JMX</h4>
<p>JMX in the JDK have features for authentication and also for using secure connections over SSL. You have to refer to the SUN documentation how to use this:</p>
<ul class="alternate" type="square"><li><a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html" rel="nofollow">http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html</a></li><li><a shape="rect" class="external-link" href="http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html" rel="nofollow">http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html</a></li></ul>
-
<h4><a shape="rect" name="CamelJMX-JMXinsideanApplicationServer"></a>JMX inside an Application Server</h4>
<h5><a shape="rect" name="CamelJMX-Tomcat6"></a>Tomcat 6</h5>
@@ -327,9 +325,6 @@ service:jmx:rmi://localhost:<connecto
<p>2. Alter your JBoss instance to use the Platform MBean server.<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>
@@ -353,7 +348,6 @@ java.lang.SecurityException: Unauthorize
</div></div>
<p>To resolve this you should disable the JMX agent in Camel, see section <em>Disabling JMX instrumentation agent in Camel</em></p>
-
<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>
@@ -373,9 +367,6 @@ java.lang.SecurityException: Unauthorize
</div></div>
<p>If you wish to change the Java 5 JMX settings you can use various <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html#properties" rel="nofollow">JMX system properties</a></p>
-
-
-
<p>For example you can enable remote JMX connections to the Sun JMX connector, via setting the following environment variable (using <b>set</b> or <b>export</b> 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.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
@@ -472,7 +463,7 @@ context.getManagementStrategy().getManag
<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 Camel > 2.9.0 support JMX Notification for fine grained trace events.<br clear="none">
+<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>
@@ -480,11 +471,8 @@ This can either be done when configuring
<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>
-
-
<p><span class="image-wrap" style=""><img src="camel-jmx.data/jconsole_trace_notifications.png" style="border: 1px solid black"></span></p>
-
<h3><a shape="rect" name="CamelJMX-UsingJMXforyourownCamelCode"></a>Using JMX for your own Camel Code</h3>
<h4><a shape="rect" name="CamelJMX-RegisteringyourownManagedEndpoints"></a>Registering your own Managed Endpoints</h4>
@@ -528,7 +516,7 @@ public class CustomEndpoint extends Mock
]]></script>
</div></div>
-<p>Notice from Camel 2.9 onwards its encouraged to use the <tt>@ManagedResource</tt>, <tt>@ManagedAttribute</tt>, and <tt>@ManagedOperation</tt> from the <tt>org.apache.camel.api.management</tt> package. This allows your custom code to not depend on Spring JARs.</p>
+<p>Notice from <b>Camel 2.9</b> onwards its encouraged to use the <tt>@ManagedResource</tt>, <tt>@ManagedAttribute</tt>, and <tt>@ManagedOperation</tt> from the <tt>org.apache.camel.api.management</tt> package. This allows your custom code to not depend on Spring JARs.</p>
<h4><a shape="rect" name="CamelJMX-ProgrammingyourownManagedServices"></a>Programming your own Managed Services</h4>
@@ -538,7 +526,7 @@ public class CustomEndpoint extends Mock
<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>
-<p>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.</p>
+<p>Now in <b>Camel 2.1</b> you can do this for all the objects that Camel registers for management which are quite a bunch, but not all.</p>
<p>For services which do not implement this <tt>ManagementAware</tt> interface then Camel will fallback to using default wrappers as defined in the table below:</p>
@@ -565,7 +553,7 @@ public class CustomEndpoint extends Mock
<h4><a shape="rect" name="CamelJMX-Managementnamingpattern"></a>Management naming pattern</h4>
<p><b>Available as of Camel 2.10</b></p>
-<p>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 <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>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
@@ -603,11 +591,11 @@ org.apache.camel:context=localhost/myCam
<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>
-<ul class="alternate" type="square"><li>non OSGI: #name#-#counter#</li><li>OSGi: #bundleId#<del>#name#</del>#counter#</li></ul>
+<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 CamelContext 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 JMXMBeanRegistry.</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">
@@ -622,7 +610,7 @@ org.apache.camel:context=localhost/myCam
]]></script>
</div></div>
-<p>In Java you can configure the <tt>managementNamePattern</tt> as follows:</p>
+<p>In Java, you can configure the <tt>managementNamePattern</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[
context.getManagementNameStrategy().setNamePattern("#name#");
@@ -636,20 +624,19 @@ context.getManagementNameStrategy().setN
]]></script>
</div></div>
-<p>You may want to do this in OSGi environments in case you do not want the bundleId as part of the mbean names. As the 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 bundleId 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#">
]]></script>
</div></div>
-<p>Note this requires that myCamel is unique in the entire JVM. If you install a 2nd Camel application that has the same <tt>CamelContext</tt> id and <tt>managementNamePattern</tt> then Camel will fail upon starting and report a MBean already exists exception.</p>
-
+<p>Note this requires that <tt>myCamel</tt> is unique in the entire JVM. If you install a 2nd Camel application that has the same <tt>CamelContext</tt> id and <tt>managementNamePattern</tt> then Camel will fail upon starting, and report a MBean already exists exception.</p>
<h4><a shape="rect" name="CamelJMX-ManagementStrategy"></a>ManagementStrategy</h4>
<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 to easier provide an adapter for other management products. In additional 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 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>
<h4><a shape="rect" name="CamelJMX-Configuringlevelofgranularityforperformancestatistics"></a>Configuring level of granularity for performance statistics</h4>
@@ -659,19 +646,17 @@ 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>
-
-
-<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">
<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
// only enable routes when Camel starts
- context.getManagementStrategy().setSatisticsLevel(ManagementStatisticsLevel.RoutesOnly);
+ context.getManagementStrategy().setStatisticsLevel(ManagementStatisticsLevel.RoutesOnly);
]]></script>
</div></div>
@@ -685,7 +670,6 @@ context.getManagementNameStrategy().setN
]]></script>
</div></div>
-
<h3><a shape="rect" name="CamelJMX-SeeAlso"></a>See Also</h3>
<ul class="alternate" type="square"><li><a shape="rect" href="management-example.html" title="Management Example">Management Example</a></li><li><a shape="rect" href="why-is-my-processor-not-showing-up-in-jconsole.html" title="Why is my processor not showing up in JConsole">Why is my processor not showing up in JConsole</a></li></ul>