lebert Suconic
> Sent: Saturday, August 12, 2023 5:35:59 PM
> To: users@activemq.apache.org
> Subject: Re: Hunting memory leaks
>
> Also. You should be using your consumers.
>
>
> On Sat, Aug 12, 2023 at 11:35 AM Clebert Suconic <
> clebert.suco...@gmail.com>
> wrote:
>
;
> Zasláno z Outlooku pro Android<https://aka.ms/AAb9ysg>
>
> From: Clebert Suconic
> Sent: Saturday, August 12, 2023 5:35:59 PM
> To: users@activemq.apache.org
> Subject: Re: Hunting memory leaks
>
> Also. You should be using your consumers.
>
>
> On Sat, Aug
Clebert Suconic
Sent: Saturday, August 12, 2023 5:35:59 PM
To: users@activemq.apache.org
Subject: Re: Hunting memory leaks
Also. You should be using your consumers.
On Sat, Aug 12, 2023 at 11:35 AM Clebert Suconic
wrote:
> You mean you are sending a PR or you will use null instead of “”?
will be happy for another Done
>> task. 😁
>>
>> Jan
>>
>> Zasláno z Outlooku pro Android<https://aka.ms/AAb9ysg>
>>
>> From: Clebert Suconic
>> Sent: Saturday, August 12, 2023 5:05:49 PM
>> To: users@activ
<https://aka.ms/AAb9ysg>
>
> From: Clebert Suconic
> Sent: Saturday, August 12, 2023 5:05:49 PM
> To: users@activemq.apache.org
> Subject: Re: Hunting memory leaks
>
> Just for a future reference, this is where the JMS layer protects this
> from happening:
ou're busy, I'll have created a PR by Monday
> > too. 🙂 And as a bonus, I'll get better acquaintanted with the Artemis code.
> >
> > Jan
> >
> >
> > Od: Clebert Suconic
> > Odesláno: sobota, srpna 12, 2023 4
, I'll have created a PR by Monday
> > too. 🙂 And as a bonus, I'll get better acquaintanted with the Artemis code.
> >
> > Jan
> >
> >
> > Od: Clebert Suconic
> > Odesláno: sobota, srpna 12, 2023 4:48:08 odp.
>
>
> I'll leave it up to you. If you're busy, I'll have created a PR by Monday
> too. 🙂 And as a bonus, I'll get better acquaintanted with the Artemis code.
>
> Jan
>
> ________
> Od: Clebert Suconic
> Odesláno: sobota,
.apache.org
Předmět: Re: Hunting memory leaks
The leak is because you are creating a consumer within the same
session over and over:
https://github.com/apache/activemq-artemis/blob/064018a3e9a1ba39ddbee0bbddfed3e7fccab89c/artemis-server/src/main/java/org/apache/activemq/artemis/
_FilterString = null. So
> > the filterStrings List keeps filling up by empty strings because these
> > don’t get removed based on a null value.
> >
> > Jan
> >
> > From: Jan Šmucr<mailto:jan.sm...@aimtecglobal.com>
> > Sent: pátek 11. srpna 2023 9
ty strings because these don’t get
> removed based on a null value.
>
> Jan
>
> From: Jan Šmucr<mailto:jan.sm...@aimtecglobal.com>
> Sent: pátek 11. srpna 2023 9:43
> To: users@activemq.apache.org<mailto:users@activemq.apache.org>
> Subject: RE: Hunting memory l
tecglobal.com>
Sent: pátek 11. srpna 2023 9:43
To: users@activemq.apache.org<mailto:users@activemq.apache.org>
Subject: RE: Hunting memory leaks
Hello all.
I know it’s not ideal but the broker is doing just fine (except for the leak
issue of course).
I’ve tried upgrading to 2.30.0 and
thread.join();
}
Big thanks for your help!
Jan
From: Arthur Naseef<mailto:a...@amlinv.com>
Sent: čtvrtek 10. srpna 2023 21:11
To: users@activemq.apache.org<mailto:users@activemq.apache.org>
Subject: Re: Hunting memory leaks
Creating a consumer only to consume 1 message is not ide
rted by Artemis doesn’t change over time.
>
>
> * I cannot reproduce the issue yet. It’s a production cluster, so
> today I’m going to set up my own playground.
>
>
> Jan
>
> From: Justin Bertram<mailto:jbert...@apache.org>
> Sent: středa 9. srpna 2023 17:41
>
playground.
Jan
From: Justin Bertram<mailto:jbert...@apache.org>
Sent: středa 9. srpna 2023 17:41
To: users@activemq.apache.org<mailto:users@activemq.apache.org>
Subject: Re: Hunting memory leaks
I echo Tim's recommendation to use the latest release, but I don't mean to
s
Reading the description of the problem, it sounds a lot like a consumer
leak to me. Specifically this part:
Consumers are polling queues on regular basis, some once a second
Is the client using JMS?
I recommend looking for signs of consumer leaks.
Art
On Wed, Aug 9, 2023 at 11:10 AM Clebert
I have recently chased a lot of leaks. Probably before 2.28. So I would
recommend the 2.30 upgrade for sure
Also one thing you could do is use my pet project to chase the increases.
It’s called check-leak.
You attach a remote process and produce a report for what’s growing. I
highly recommend
I echo Tim's recommendation to use the latest release, but I don't mean to
say that will certainly resolve the problem.
I can't say if you're doing anything wrong without more information. Can
you answer the following questions?
- What client library are you using?
- How often are consumers bei
On 8/9/23 08:06, Jan Šmucr wrote:
Hello.
I’m using a simple master-slave Artemis 2.26.0 cluster, and I’m noticing heap
usage growing more and more each day no matter the throughput. There’s about
670 sessions at the same time opened for producers and consumers. Consumers are
polling queues on
Hello.
I’m using a simple master-slave Artemis 2.26.0 cluster, and I’m noticing heap
usage growing more and more each day no matter the throughput. There’s about
670 sessions at the same time opened for producers and consumers. Consumers are
polling queues on regular basis, some once a second (m
20 matches
Mail list logo
