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 <patrick.reg...@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
