You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Deomisr <pa...@edf.fr> on 2017/07/25 09:06:59 UTC
Memory leak with apache artemis 2.1.0
Hi,
With my broker Mqtt configuration, it seems a memory leak appears after 3
days.
Indeed the memory increase but each full GC and GC not release enough
memory.
my JAVA_ARGS=" -XX:+PrintClassHistogram -XX:+UseG1GC -XX:+AggressiveOpts
-XX:+UseFastAccessorMethods -Xms4G -Xmx4G"
see below my broker.xml file
brokerSR.xml
<http://activemq.2283324.n4.nabble.com/file/n4728863/brokerSR.xml>
we have around 43 messages/sec
<http://activemq.2283324.n4.nabble.com/file/n4728863/nbMessageparseconde.png>
Please find below a screenshot of the memory leak :
<http://activemq.2283324.n4.nabble.com/file/n4728863/MemoryLeak.png>
Please find below a screenshot of my heapdump
<http://activemq.2283324.n4.nabble.com/file/n4728863/heapdump.png>
Can you help me to resolve this issue.
--
View this message in context: http://activemq.2283324.n4.nabble.com/Memory-leak-with-apache-artemis-2-1-0-tp4728863.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Memory leak with apache artemis 2.1.0
Posted by Deomisr <pa...@edf.fr>.
the issue is solved in 2.2.0
thanks a lot :
<http://activemq.2283324.n4.nabble.com/file/n4729051/MemoryLeaksolved.png>
--
View this message in context: http://activemq.2283324.n4.nabble.com/Memory-leak-with-apache-artemis-2-1-0-tp4728863p4729051.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Memory leak with apache artemis 2.1.0
Posted by Clebert Suconic <cl...@gmail.com>.
The way releases work at apanhe is. You propose a release in the dev list.
Then people try it and vote +1 or -1.
There is a release candidate I started yesterday. Look at the activemq dev
list.
In any case the candidate release is here.
https://repository.apache.org/content/repositories/orgapacheactivemq-1142/org/apache/activemq/apache-artemis/2.2.0/
It will be promoted as 2.2.0 in 2 days unless someone find an issue with
the release itself and -1. (Bugs won't count unless it's a horrible one)
On Wed, Jul 26, 2017 at 4:33 AM REGINA Patrick <pa...@edf.fr>
wrote:
> Hi,
>
> Where can I found artemis 2.2.0
>
> I was on the page https://activemq.apache.org/artemis/download.html and
> https://activemq.apache.org/artemis/download.html but i didn't found the
> release 2.2.0.
>
> Cordialement,
>
> Patrick REGINA
> Digital PaaS – Technical officer
> Centre d'Expertise webMethods
> EDF - DSP - CSP IT - DMA
> CC SPENCER (Sécurisation, Projets, Entreprise Numérique, Conseil,
> Expertise, Réalisation)
> Groupe Expertise en Solutions Middleware (ESM)
> 32 avenue Pablo Picasso
> 92016 Nanterre Cedex
>
> patrick.regina@edf.fr
> Tel : 01.78.66.60.79
> Fax : 01.78.66.93.47
>
>
> -----Message d'origine-----
> De : clebert.suconic@gmail.com [mailto:clebert.suconic@gmail.com]
> Envoyé : mardi 25 juillet 2017 20:29
> À : users@activemq.apache.org
> Objet : Re: Memory leak with apache artemis 2.1.0
>
> Just sent the RC for 2.2.0..
>
> I would appreciate if you could evaluate the release accordingly to that
> vote thread on the dev list.
>
> On Tue, Jul 25, 2017 at 8:47 AM, Clebert Suconic <
> clebert.suconic@gmail.com> wrote:
> > I am sending the vote thread today for 2.2.0 with that fix.
> >
> > Can you try it then. Expect it within 11:00 EST today.
> >
> > On Tue, Jul 25, 2017 at 5:35 AM Helge Waastad <he...@waastad.org> wrote:
> >>
> >> Hi,
> >> Try 2.2.0 snapshot.
> >> A few mem issues has been resolved since 2.1.0.
> >>
> >> /hw
> >>
> >> Sendt fra min iPhone
> >>
> >> > Den 25. jul. 2017 kl. 11.06 skrev Deomisr <pa...@edf.fr>:
> >> >
> >> > Hi,
> >> >
> >> > With my broker Mqtt configuration, it seems a memory leak appears
> >> > after
> >> > 3
> >> > days.
> >> > Indeed the memory increase but each full GC and GC not release
> >> > enough memory.
> >> > my JAVA_ARGS=" -XX:+PrintClassHistogram -XX:+UseG1GC
> >> > -XX:+AggressiveOpts -XX:+UseFastAccessorMethods -Xms4G -Xmx4G"
> >> >
> >> > see below my broker.xml file
> >> > brokerSR.xml
> >> > <http://activemq.2283324.n4.nabble.com/file/n4728863/brokerSR.xml>
> >> >
> >> > we have around 43 messages/sec
> >> >
> >> > <http://activemq.2283324.n4.nabble.com/file/n4728863/nbMessageparse
> >> > conde.png>
> >> >
> >> > Please find below a screenshot of the memory leak :
> >> > <http://activemq.2283324.n4.nabble.com/file/n4728863/MemoryLeak.png
> >> > >
> >> >
> >> > Please find below a screenshot of my heapdump
> >> > <http://activemq.2283324.n4.nabble.com/file/n4728863/heapdump.png>
> >> >
> >> >
> >> >
> >> >
> >> > Can you help me to resolve this issue.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > View this message in context:
> >> > http://activemq.2283324.n4.nabble.com/Memory-leak-with-apache-artem
> >> > is-2-1-0-tp4728863.html Sent from the ActiveMQ - User mailing list
> >> > archive at Nabble.com.
> >>
> > --
> > Clebert Suconic
>
>
>
> --
> Clebert Suconic
>
>
>
> Ce message et toutes les pièces jointes (ci-après le 'Message') sont
> établis à l'intention exclusive des destinataires et les informations qui y
> figurent sont strictement confidentielles. Toute utilisation de ce Message
> non conforme à sa destination, toute diffusion ou toute publication totale
> ou partielle, est interdite sauf autorisation expresse.
>
> Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de
> le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou
> partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de
> votre système, ainsi que toutes ses copies, et de n'en garder aucune trace
> sur quelque support que ce soit. Nous vous remercions également d'en
> avertir immédiatement l'expéditeur par retour du message.
>
> Il est impossible de garantir que les communications par messagerie
> électronique arrivent en temps utile, sont sécurisées ou dénuées de toute
> erreur ou virus.
> ____________________________________________________
>
> This message and any attachments (the 'Message') are intended solely for
> the addressees. The information contained in this Message is confidential.
> Any use of information contained in this Message not in accord with its
> purpose, any dissemination or disclosure, either whole or partial, is
> prohibited except formal approval.
>
> If you are not the addressee, you may not copy, forward, disclose or use
> any part of it. If you have received this message in error, please delete
> it and all copies from your system and notify the sender immediately by
> return message.
>
> E-mail communication cannot be guaranteed to be timely secure, error or
> virus-free.
>
--
Clebert Suconic
RE: Memory leak with apache artemis 2.1.0
Posted by REGINA Patrick <pa...@edf.fr>.
Hi,
Where can I found artemis 2.2.0
I was on the page https://activemq.apache.org/artemis/download.html and https://activemq.apache.org/artemis/download.html but i didn't found the release 2.2.0.
Cordialement,
Patrick REGINA
Digital PaaS – Technical officer
Centre d'Expertise webMethods
EDF - DSP - CSP IT - DMA
CC SPENCER (Sécurisation, Projets, Entreprise Numérique, Conseil, Expertise, Réalisation)
Groupe Expertise en Solutions Middleware (ESM)
32 avenue Pablo Picasso
92016 Nanterre Cedex
patrick.regina@edf.fr
Tel : 01.78.66.60.79
Fax : 01.78.66.93.47
-----Message d'origine-----
De : clebert.suconic@gmail.com [mailto:clebert.suconic@gmail.com]
Envoyé : mardi 25 juillet 2017 20:29
À : users@activemq.apache.org
Objet : Re: Memory leak with apache artemis 2.1.0
Just sent the RC for 2.2.0..
I would appreciate if you could evaluate the release accordingly to that vote thread on the dev list.
On Tue, Jul 25, 2017 at 8:47 AM, Clebert Suconic <cl...@gmail.com> wrote:
> I am sending the vote thread today for 2.2.0 with that fix.
>
> Can you try it then. Expect it within 11:00 EST today.
>
> On Tue, Jul 25, 2017 at 5:35 AM Helge Waastad <he...@waastad.org> wrote:
>>
>> Hi,
>> Try 2.2.0 snapshot.
>> A few mem issues has been resolved since 2.1.0.
>>
>> /hw
>>
>> Sendt fra min iPhone
>>
>> > Den 25. jul. 2017 kl. 11.06 skrev Deomisr <pa...@edf.fr>:
>> >
>> > Hi,
>> >
>> > With my broker Mqtt configuration, it seems a memory leak appears
>> > after
>> > 3
>> > days.
>> > Indeed the memory increase but each full GC and GC not release
>> > enough memory.
>> > my JAVA_ARGS=" -XX:+PrintClassHistogram -XX:+UseG1GC
>> > -XX:+AggressiveOpts -XX:+UseFastAccessorMethods -Xms4G -Xmx4G"
>> >
>> > see below my broker.xml file
>> > brokerSR.xml
>> > <http://activemq.2283324.n4.nabble.com/file/n4728863/brokerSR.xml>
>> >
>> > we have around 43 messages/sec
>> >
>> > <http://activemq.2283324.n4.nabble.com/file/n4728863/nbMessageparse
>> > conde.png>
>> >
>> > Please find below a screenshot of the memory leak :
>> > <http://activemq.2283324.n4.nabble.com/file/n4728863/MemoryLeak.png
>> > >
>> >
>> > Please find below a screenshot of my heapdump
>> > <http://activemq.2283324.n4.nabble.com/file/n4728863/heapdump.png>
>> >
>> >
>> >
>> >
>> > Can you help me to resolve this issue.
>> >
>> >
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> > http://activemq.2283324.n4.nabble.com/Memory-leak-with-apache-artem
>> > is-2-1-0-tp4728863.html Sent from the ActiveMQ - User mailing list
>> > archive at Nabble.com.
>>
> --
> Clebert Suconic
--
Clebert Suconic
Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires et les informations qui y figurent sont strictement confidentielles. Toute utilisation de ce Message non conforme à sa destination, toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse.
Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre système, ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Nous vous remercions également d'en avertir immédiatement l'expéditeur par retour du message.
Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, sont sécurisées ou dénuées de toute erreur ou virus.
____________________________________________________
This message and any attachments (the 'Message') are intended solely for the addressees. The information contained in this Message is confidential. Any use of information contained in this Message not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval.
If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return message.
E-mail communication cannot be guaranteed to be timely secure, error or virus-free.
Re: Memory leak with apache artemis 2.1.0
Posted by Clebert Suconic <cl...@gmail.com>.
Just sent the RC for 2.2.0..
I would appreciate if you could evaluate the release accordingly to
that vote thread on the dev list.
On Tue, Jul 25, 2017 at 8:47 AM, Clebert Suconic
<cl...@gmail.com> wrote:
> I am sending the vote thread today for 2.2.0 with that fix.
>
> Can you try it then. Expect it within 11:00 EST today.
>
> On Tue, Jul 25, 2017 at 5:35 AM Helge Waastad <he...@waastad.org> wrote:
>>
>> Hi,
>> Try 2.2.0 snapshot.
>> A few mem issues has been resolved since 2.1.0.
>>
>> /hw
>>
>> Sendt fra min iPhone
>>
>> > Den 25. jul. 2017 kl. 11.06 skrev Deomisr <pa...@edf.fr>:
>> >
>> > Hi,
>> >
>> > With my broker Mqtt configuration, it seems a memory leak appears after
>> > 3
>> > days.
>> > Indeed the memory increase but each full GC and GC not release enough
>> > memory.
>> > my JAVA_ARGS=" -XX:+PrintClassHistogram -XX:+UseG1GC -XX:+AggressiveOpts
>> > -XX:+UseFastAccessorMethods -Xms4G -Xmx4G"
>> >
>> > see below my broker.xml file
>> > brokerSR.xml
>> > <http://activemq.2283324.n4.nabble.com/file/n4728863/brokerSR.xml>
>> >
>> > we have around 43 messages/sec
>> >
>> > <http://activemq.2283324.n4.nabble.com/file/n4728863/nbMessageparseconde.png>
>> >
>> > Please find below a screenshot of the memory leak :
>> > <http://activemq.2283324.n4.nabble.com/file/n4728863/MemoryLeak.png>
>> >
>> > Please find below a screenshot of my heapdump
>> > <http://activemq.2283324.n4.nabble.com/file/n4728863/heapdump.png>
>> >
>> >
>> >
>> >
>> > Can you help me to resolve this issue.
>> >
>> >
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> > http://activemq.2283324.n4.nabble.com/Memory-leak-with-apache-artemis-2-1-0-tp4728863.html
>> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
> --
> Clebert Suconic
--
Clebert Suconic
Re: Memory leak with apache artemis 2.1.0
Posted by Clebert Suconic <cl...@gmail.com>.
I am sending the vote thread today for 2.2.0 with that fix.
Can you try it then. Expect it within 11:00 EST today.
On Tue, Jul 25, 2017 at 5:35 AM Helge Waastad <he...@waastad.org> wrote:
> Hi,
> Try 2.2.0 snapshot.
> A few mem issues has been resolved since 2.1.0.
>
> /hw
>
> Sendt fra min iPhone
>
> > Den 25. jul. 2017 kl. 11.06 skrev Deomisr <pa...@edf.fr>:
> >
> > Hi,
> >
> > With my broker Mqtt configuration, it seems a memory leak appears after 3
> > days.
> > Indeed the memory increase but each full GC and GC not release enough
> > memory.
> > my JAVA_ARGS=" -XX:+PrintClassHistogram -XX:+UseG1GC -XX:+AggressiveOpts
> > -XX:+UseFastAccessorMethods -Xms4G -Xmx4G"
> >
> > see below my broker.xml file
> > brokerSR.xml
> > <http://activemq.2283324.n4.nabble.com/file/n4728863/brokerSR.xml>
> >
> > we have around 43 messages/sec
> > <
> http://activemq.2283324.n4.nabble.com/file/n4728863/nbMessageparseconde.png
> >
> >
> > Please find below a screenshot of the memory leak :
> > <http://activemq.2283324.n4.nabble.com/file/n4728863/MemoryLeak.png>
> >
> > Please find below a screenshot of my heapdump
> > <http://activemq.2283324.n4.nabble.com/file/n4728863/heapdump.png>
> >
> >
> >
> >
> > Can you help me to resolve this issue.
> >
> >
> >
> >
> >
> > --
> > View this message in context:
> http://activemq.2283324.n4.nabble.com/Memory-leak-with-apache-artemis-2-1-0-tp4728863.html
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
> --
Clebert Suconic
Re: Memory leak with apache artemis 2.1.0
Posted by Helge Waastad <he...@waastad.org>.
Hi,
Try 2.2.0 snapshot.
A few mem issues has been resolved since 2.1.0.
/hw
Sendt fra min iPhone
> Den 25. jul. 2017 kl. 11.06 skrev Deomisr <pa...@edf.fr>:
>
> Hi,
>
> With my broker Mqtt configuration, it seems a memory leak appears after 3
> days.
> Indeed the memory increase but each full GC and GC not release enough
> memory.
> my JAVA_ARGS=" -XX:+PrintClassHistogram -XX:+UseG1GC -XX:+AggressiveOpts
> -XX:+UseFastAccessorMethods -Xms4G -Xmx4G"
>
> see below my broker.xml file
> brokerSR.xml
> <http://activemq.2283324.n4.nabble.com/file/n4728863/brokerSR.xml>
>
> we have around 43 messages/sec
> <http://activemq.2283324.n4.nabble.com/file/n4728863/nbMessageparseconde.png>
>
> Please find below a screenshot of the memory leak :
> <http://activemq.2283324.n4.nabble.com/file/n4728863/MemoryLeak.png>
>
> Please find below a screenshot of my heapdump
> <http://activemq.2283324.n4.nabble.com/file/n4728863/heapdump.png>
>
>
>
>
> Can you help me to resolve this issue.
>
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Memory-leak-with-apache-artemis-2-1-0-tp4728863.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.