Awesome, thanks for the feedback. We'd still want to fix the actual issue.
If you get time, if you can file a JIRA, that would be great.

Jon

On Tue, Feb 11, 2020 at 6:01 PM COURTAULT Francois <
francois.courta...@thalesgroup.com> wrote:

> Hello Jonathan,
>
> We did the test (remove tomee.mp.scan = all  entry in system.properties)
> with TomEE MP and it solves the issue we have:  a lot of opentracing
> objects created.
> We don't have this issue (a lot of opentracing objects created) in TomEE
> Plus because this entry doesn't exist in system.properties !!!
>
> Best Regards.
>
> -----Original Message-----
> From: COURTAULT Francois
> Sent: mardi 11 février 2020 10:32
> To: users@tomee.apache.org
> Subject: RE: TomEE microprofile memory consumption
>
> Hello Jonathan,
>
> As I have mentioned, we see the issue in TomEE MP but not in TomEE Plus !
> So I did a comparison of the 2 flavors: lib + conf
>
> The only difference I have seen is in the system.properties where I have
> the line below in TomEE MP and not this one in TomEE Plus !
> This could explain. We will try to remove this line to see if it solves
> the memory issue we have and will let you know.
>
> Best Regards.
>
> -----Original Message-----
> From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
> Sent: lundi 10 février 2020 23:14
> To: users@tomee.apache.org
> Subject: Re: TomEE microprofile memory consumption
>
> Allow me start over, if I may.
>
> What are you seeing in your memory dumps that's a concern - a large number
> of ScopeImpl objects? Could you provide some screenshots from VisualVM for
> us? I'd be interested in object counts, and whether there are references,
> and if so, what they are.
>
> The TaskThread comes from Tomcat. It being present doesn't sound like an
> issue, but I appreciate you've asked because you have some concern - can
> you provide some more context?
>
> > You didn't answer to this question: Is there a way to disable
> > opentracing
> in TomEE MP ? Is it possible ?
>
> Its a setting in the Geronimo OpenTracing project:
> https://github.com/apache/geronimo-opentracing. Try setting
> geronimo.opentracing.filter.active to false (an entry in
> conf/system.properties should do the trick).
>
> Jon
>
> On Mon, Feb 10, 2020 at 6:46 PM COURTAULT Francois <
> francois.courta...@thalesgroup.com> wrote:
>
> > Hello Jonathan,
> >
> > Quite complex for us what you ask for.
> >
> > BTW, have you any idea about this
> > org.apache.tomcat.util.threads.TaskThread in the memory dump we have.
> > Where could it come from ?
> >
> > You didn't answer to this question: Is there a way to disable
> > opentracing in TomEE MP ? Is it possible ?
> >
> > Best Regards.
> >
> > -----Original Message-----
> > From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
> > Sent: lundi 10 février 2020 18:21
> > To: users@tomee.apache.org
> > Subject: Re: TomEE microprofile memory consumption
> >
> > > I can provide you some memory dumps if you want .
> >
> > Some details on how to reproduce with a small sample would be helpful.
> > Memory dumps tend to be quite large and contain confidential
> > information, so we prefer to not exchange those on the list.
> >
> > Jon
> >
> > On Mon, Feb 10, 2020 at 5:10 PM COURTAULT Francois <
> > francois.courta...@thalesgroup.com> wrote:
> >
> > > Hello everyone,
> > >
> > > We have 2 microservices: one using TomEE Plus and the other using
> > > TomEE
> > MP.
> > > These 2 µS don't use at all OpenTracing features: no @Trace ....
> > > We have no memory issue with the µS using TomEE Plus. This is
> > > strange because TomEE Plus  somehow is a superset of TomEE MP.
> > >
> > > The issue is due to the usage of
> > > org.apache.geronimo.microprofile.opentracing.impl.ScopeImpl but we
> > > don't know what trigger that usage.
> > > We also see a lot of org.apache.tomcat.util.threads.TaskThread
> > > (don't know where it comes from) which uses the above ScopeImpl.
> > >
> > > I can provide you some memory dumps if you want .
> > >
> > > Is there a way to disable opentracing in TomEE MP ?
> > >
> > > Best Regards.
> > >
> > >
> > >
> > >
> >
>

Reply via email to