You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by "KARR, DAVID" <dk...@att.com> on 2016/10/05 15:14:04 UTC
Reference to a version "3.0.1" in metrics doc, and classloader leaks
I noticed on http://camel.apache.org/metrics-component.html the following text:
----------------
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.
----------------
I could use some clarification of this.
First, I'm not aware of any "3.0.1" release of Camel. I assume this is a typo? What version should this be referring to?
Second, can anyone describe in more detail how the lack of a cleanup process on exit could lead to leaks of any kind?
RE: Reference to a version "3.0.1" in metrics doc, and classloader
leaks
Posted by "KARR, DAVID" <dk...@att.com>.
> -----Original Message-----
> From: KARR, DAVID
> Sent: Wednesday, October 05, 2016 8:36 AM
> To: users@camel.apache.org
> Subject: RE: Reference to a version "3.0.1" in metrics doc, and
> classloader leaks
>
> > -----Original Message-----
> > From: KARR, DAVID
> > Sent: Wednesday, October 05, 2016 8:14 AM
> > To: users@camel.apache.org
> > Subject: Reference to a version "3.0.1" in metrics doc, and
> > classloader leaks
> >
> > I noticed on http://camel.apache.org/metrics-component.html the
> > following text:
> > ----------------
> > 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.
> > ----------------
> >
> > I could use some clarification of this.
> >
> > First, I'm not aware of any "3.0.1" release of Camel. I assume this
> > is a typo? What version should this be referring to?
>
> Ah. I'm guessing the version number here refers to the version of the
> "DropWizard Metrics" library, not the version of Camel. That statement
> should be amended to reflect that.
In fact, I see that there's no mention anywhere on this page that this is integrating the DropWizard Metrics package. I see it mentioned in examples in the codebase, but the docs really should clarify this.
RE: Reference to a version "3.0.1" in metrics doc, and classloader
leaks
Posted by "KARR, DAVID" <dk...@att.com>.
> -----Original Message-----
> From: KARR, DAVID
> Sent: Wednesday, October 05, 2016 8:14 AM
> To: users@camel.apache.org
> Subject: Reference to a version "3.0.1" in metrics doc, and classloader
> leaks
>
> I noticed on http://camel.apache.org/metrics-component.html the
> following text:
> ----------------
> 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.
> ----------------
>
> I could use some clarification of this.
>
> First, I'm not aware of any "3.0.1" release of Camel. I assume this is
> a typo? What version should this be referring to?
Ah. I'm guessing the version number here refers to the version of the "DropWizard Metrics" library, not the version of Camel. That statement should be amended to reflect that.
> Second, can anyone describe in more detail how the lack of a cleanup
> process on exit could lead to leaks of any kind?
Re: Reference to a version "3.0.1" in metrics doc, and classloader leaks
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Thanks I added the word dropwizard to the version
On Wed, Oct 5, 2016 at 11:14 AM, KARR, DAVID <dk...@att.com> wrote:
> I noticed on http://camel.apache.org/metrics-component.html the following text:
> ----------------
> 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.
> ----------------
>
> I could use some clarification of this.
>
> First, I'm not aware of any "3.0.1" release of Camel. I assume this is a typo? What version should this be referring to?
>
> Second, can anyone describe in more detail how the lack of a cleanup process on exit could lead to leaks of any kind?
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Reference to a version "3.0.1" in metrics doc, and classloader leaks
Posted by Claus Ibsen <cl...@gmail.com>.
You can have leaks if you do re-deployment in the same JVM like an app server.
You are also welcome to check newer version of DropWizard what APIs it
may have or if there is some auto-cleanup or something.
On Wed, Oct 5, 2016 at 11:14 AM, KARR, DAVID <dk...@att.com> wrote:
> I noticed on http://camel.apache.org/metrics-component.html the following text:
> ----------------
> 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.
> ----------------
>
> I could use some clarification of this.
>
> First, I'm not aware of any "3.0.1" release of Camel. I assume this is a typo? What version should this be referring to?
>
> Second, can anyone describe in more detail how the lack of a cleanup process on exit could lead to leaks of any kind?
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2