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.
