Camel-Metrics component -- is it safe to use in Production?

[xlogger <xl...@gmail.com>]

In the documentation http://camel.apache.org/metrics-component.html, it
mentioned that 

MetricRegistry 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 OutOfMemoryErrors in
some cases.

May I know what were the cases that might leads to the OOM issue? Was it
still the case in the latest Camel 2.16.0 version or the issue has been
fixed and safe to use in Production environment?

Is there any alternatives that could achieve the same functionality?





--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Metrics-component-is-it-safe-to-use-in-Production-tp5772630.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel-Metrics component -- is it safe to use in Production?

[Joakim Bjørnstad <jo...@gmail.com>]

Hello,

Camel 2.16.0 uses metrics 3.1.2 but as far as I know, there is still
an issue with this in metrics.
Related metrics issue: https://github.com/dropwizard/metrics/issues/742

The github issue explains some of the circumstances. Problems with
ThreadLocals not being garbage collected when deploying/undeploying to
certain servlet containers, Tomcat is mentioned.

We use camel-metrics in production. No issues on Jboss EAP 6.1 thus
far. In my current project I have used camel standalone and no issues
thus far either.

Alternatives, not as a camel component as far as I know. Camel does
gather its own statistics for exchanges though, exposed as JMX.
But with metrics it is very easy to expose a REST endpoint that just
dumps the metrics registry as json. Like 6 lines of code to put it on
the edge.


On Wed, Oct 14, 2015 at 7:34 AM, xlogger <xl...@gmail.com> wrote:
> In the documentation http://camel.apache.org/metrics-component.html, it
> mentioned that
>
> MetricRegistry 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 OutOfMemoryErrors in
> some cases.
>
> May I know what were the cases that might leads to the OOM issue? Was it
> still the case in the latest Camel 2.16.0 version or the issue has been
> fixed and safe to use in Production environment?
>
> Is there any alternatives that could achieve the same functionality?
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Camel-Metrics-component-is-it-safe-to-use-in-Production-tp5772630.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Kind regards
Joakim Bjørnstad