Hi, We do dev in prodđŸ˜‰ I actually since posting built the 2.2.0-SN from yesterday and I'll see if it makes any difference.
I'll add the detection option if needed Thx. /hw Sendt fra min iPhone > Den 3. jun. 2017 kl. 09.19 skrev Michael André Pearce > <michael.andre.pea...@me.com>: > > If you have the ability (not sure if this is a dev or a prod env) as clebert > mentions at there are some changes in master for MQTT protocol since 2.1.0 > release, if you have any chance to build and deploy master? > > On the netty front there's a system property > -Dio.netty.leakDetection.level=advanced > If you add this and rerun, this will output if there's any leak. To eliminate > or prove that one. > > Cheers > Mike > > > Sent from my iPhone > >> On 3 Jun 2017, at 07:18, hwaastad <he...@waastad.org> wrote: >> >> Hi guys, >> and thx for answering. >> >> a quick summary of my setup: >> 1. Its 2.1.0 so I'm not running any snapshot >> 2. The load is pretty constant.(performance checks from nagios), approx >> 1.1GB data per month, 2.5 mill entries over MQTT. >> 3. We've been running activemq with virtualdestinations (mqtt->jms) earlier >> and never had any issues. >> 4. Memory usage is increasing. I'll see if I can get more stats. >> 5. I did change my setup yesterday, skipping clustering and running a >> standalone instance. just to see if clustering was the issue. >> 6. If there are mem leaks in netty, is there any workaround? >> >> >> /hw >> >> >> >> -- >> View this message in context: >> http://activemq.2283324.n4.nabble.com/artemis-2-1-0-logging-disaster-tp4726922p4726986.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
