Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 43391200C89 for ; Sat, 3 Jun 2017 09:37:44 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 42170160BCD; Sat, 3 Jun 2017 07:37:44 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8C305160BBE for ; Sat, 3 Jun 2017 09:37:43 +0200 (CEST) Received: (qmail 14171 invoked by uid 500); 3 Jun 2017 07:37:42 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 14160 invoked by uid 99); 3 Jun 2017 07:37:42 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Jun 2017 07:37:42 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E5A52C24E4 for ; Sat, 3 Jun 2017 07:37:41 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.614 X-Spam-Level: X-Spam-Status: No, score=0.614 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_TRY_3LD=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id ld8T4M-la1iK for ; Sat, 3 Jun 2017 07:37:39 +0000 (UTC) Received: from smtp.domeneshop.no (smtp.domeneshop.no [194.63.252.55]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 9842F5F2AE for ; Sat, 3 Jun 2017 07:37:39 +0000 (UTC) Received: from [2001:4640:3e3d:0:bc07:114f:b5f7:f4e2] (port=61276) by smtp.domeneshop.no with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dH3cv-0007QY-TD for users@activemq.apache.org; Sat, 03 Jun 2017 09:37:37 +0200 From: Helge Waastad Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Date: Sat, 3 Jun 2017 09:37:36 +0200 Subject: Re: artemis 2.2.0 logging disaster Message-Id: References: <1496393053.6455.18.camel@waastad.org> <1496470728195-4726986.post@n4.nabble.com> In-Reply-To: To: users@activemq.apache.org X-Mailer: iPhone Mail (14F89) archived-at: Sat, 03 Jun 2017 07:37:44 -0000 Hi, We do dev in prod=F0=9F=98=89 I actually since posting built the 2.2.0-SN from yesterday and I'll see if i= t 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=C3=A9 Pearce : >=20 > If you have the ability (not sure if this is a dev or a prod env) as clebe= rt 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? >=20 > On the netty front there's a system property=20 > -Dio.netty.leakDetection.level=3Dadvanced > If you add this and rerun, this will output if there's any leak. To elimin= ate or prove that one. >=20 > Cheers > Mike >=20 >=20 > Sent from my iPhone >=20 >> On 3 Jun 2017, at 07:18, hwaastad wrote: >>=20 >> Hi guys, >> and thx for answering. >>=20 >> 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) earli= er >> 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? >>=20 >>=20 >> /hw >>=20 >>=20 >>=20 >> -- >> View this message in context: http://activemq.2283324.n4.nabble.com/artem= is-2-1-0-logging-disaster-tp4726922p4726986.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.