Author: buildbot
Date: Thu Oct 6 12:19:31 2016
New Revision: 998958
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/metrics-component.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/metrics-component.html
==============================================================================
--- websites/production/camel/content/metrics-component.html (original)
+++ websites/production/camel/content/metrics-component.html Thu Oct 6
12:19:31 2016
@@ -116,7 +116,7 @@ public static class MyConfig extends Sin
return registry;
}
}]]></script>
-</div></div><div class="confluence-information-macro
confluence-information-macro-warning"><span class="aui-icon aui-icon-small
aui-iconfont-error confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p><code>MetricRegistry</code> uses
internal thread(s) for reporting. There is no public API in version 3.0.1 for
users to clean up on exit. Thus using Camel Metrics Component leads to Java
classloader leak and my cause <code>OutOfMemoryErrors</code> in some
cases.</p></div></div><h3 id="MetricsComponent-Usage">Usage</h3><p>Each metric
has type and name. Supported types are <a shape="rect"
href="#MetricsComponent-counter">counter</a>, <a shape="rect"
href="#MetricsComponent-histogram">histogram</a>, <a shape="rect"
href="#MetricsComponent-meter">meter</a> and <a shape="rect"
href="#MetricsComponent-timer">timer</a>. Metric name is simple string. If
metric type is not provided then type meter is used by default.</p><h4
id="MetricsComponent-He
aders">Headers</h4><p>Metric name defined in URI can be overridden by using
header with name <code>CamelMetricsName</code>.</p><p>For example</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><div class="confluence-information-macro
confluence-information-macro-warning"><span class="aui-icon aui-icon-small
aui-iconfont-error confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p><code>MetricRegistry</code> uses
internal thread(s) for reporting. There is no public API in DropWizard version
3.0.1 for users to clean up on exit. Thus using Camel Metrics Component leads
to Java classloader leak and my cause <code>OutOfMemoryErrors</code> in some
cases.</p></div></div><h3 id="MetricsComponent-Usage">Usage</h3><p>Each metric
has type and name. Supported types are <a shape="rect"
href="#MetricsComponent-counter">counter</a>, <a shape="rect"
href="#MetricsComponent-histogram">histogram</a>, <a shape="rect"
href="#MetricsComponent-meter">meter</a> and <a shape="rect"
href="#MetricsComponent-timer">timer</a>. Metric name is simple string. If
metric type is not provided then type meter is used by default.</p><h4
id="MetricsC
omponent-Headers">Headers</h4><p>Metric name defined in URI can be overridden
by using header with name <code>CamelMetricsName</code>.</p><p>For
example</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[from("direct:in")
.setHeader(MetricsConstants.HEADER_METRIC_NAME,
constant("new.name"))
.to("metrics:counter:name.not.used")