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 7030B200C16 for ; Thu, 9 Feb 2017 13:23:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6ED0C160B50; Thu, 9 Feb 2017 12:23:04 +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 B8FB9160B4C for ; Thu, 9 Feb 2017 13:23:03 +0100 (CET) Received: (qmail 9808 invoked by uid 500); 9 Feb 2017 12:23:02 -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 9797 invoked by uid 99); 9 Feb 2017 12:23:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Feb 2017 12:23:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 0E81AC0027 for ; Thu, 9 Feb 2017 12:23:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.794 X-Spam-Level: *** X-Spam-Status: No, score=3.794 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_TRY_3LD=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id KrX4LkI9XvOo for ; Thu, 9 Feb 2017 12:22:57 +0000 (UTC) Received: from mail-qk0-f169.google.com (mail-qk0-f169.google.com [209.85.220.169]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id EA2CA5FC84 for ; Thu, 9 Feb 2017 12:22:56 +0000 (UTC) Received: by mail-qk0-f169.google.com with SMTP id 11so2018508qkl.3 for ; Thu, 09 Feb 2017 04:22:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=NwzRwOCjk5dl6LYlLEP7WTdlO7aargjHBAfyRC7qfcg=; b=PoTPrs0YFQ3pOj+4llBnePV0yW3mIY4QKv3n/mlW2kTlrfdgsb8l2nR4Vhdi1mP8eV uu0x/10RqMMBt17Iqfpfu2sRwLM2RaLqktTkDmqH2GPOb3F01tnJrR/BD25ubUkJ1xMn PpAMs+A1Od6IY/wkzprVDo7HxRLQvMp8qWeimMu31IKdJVF2Z4QR961D2HMcz17dcDyJ 3oxC+X+fR3VVMI69UlQU+jQ60p+2w7cGkcUxp3mTRXgpxg1f33PDdlvf2Ru8qV51ha/X r1h8j0eHWuqtmb2v/2bdRtcDG+jVOaTtDEvfahGblkVK1yBBnRf8sYZY5MVHD5P/fZ94 bQiw== X-Gm-Message-State: AMke39k57aeYZodSASl3IoV+d/cSJpqbFcBAb3uLMU4PdP6wkTBwR/pbgNHjRrw6MMMMTirI1uoC0XqfCbAkJx4r X-Received: by 10.55.5.66 with SMTP id 63mr2731386qkf.163.1486642972734; Thu, 09 Feb 2017 04:22:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.148.80 with HTTP; Thu, 9 Feb 2017 04:22:52 -0800 (PST) In-Reply-To: <1486463625907-4721678.post@n4.nabble.com> References: <1485788293667-4721395.post@n4.nabble.com> <1485862037305-4721417.post@n4.nabble.com> <1485954137792-4721470.post@n4.nabble.com> <1486121944351-4721562.post@n4.nabble.com> <1486463625907-4721678.post@n4.nabble.com> From: Martyn Taylor Date: Thu, 9 Feb 2017 12:22:52 +0000 Message-ID: Subject: Re: ARTEMIS: bad-performance behaviour after 7-10 days of usage To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=001a114c814e4c4e9e0548180a70 archived-at: Thu, 09 Feb 2017 12:23:04 -0000 --001a114c814e4c4e9e0548180a70 Content-Type: text/plain; charset=UTF-8 Francesco, I think I've identified the cause of this problem. There were two issues which are now fixed as part of: https://github.com/apache/activemq-artemis/pull/1002 I'll get these fixes cherry-picked onto Artemis 1.x stream. I plan on doing a 1.5.3 (with these changes included) within the next couple of days. Cheers Martyn On Tue, Feb 7, 2017 at 10:33 AM, francesco81 wrote: > Hi Martyn, > I'll be happy to enjoy the IRC chat as soon as I can. > Effectively, your words about the "treating as new subscription" would > explain the issue with retained messages. > However there's still something that I don't understand: for example why > also the non-retained messages are resent on resubscription. Regardless if > retained or not, it seems that all messages persist on queue (or, in case > of > retained, they persist on address and one more reference is added on queue > at each resubscription... I don't know, I'm trying to guess) and are never > discarded. > How are they managed by artemis? In a scenario where clients never connect > with "cleanSession=false" (that is our usecase), I thought: > - non-retained messages are removed from address (and references from > queues) once they are consumed by clients (or immediatly if no client is > connected). > - retained messages are removed from address when a new one arrives (and > the > reference to the new one substitutes the previous on the queue). > Is not so? I'm wrong somewhere? > > Again, thanks for your patience. > > Francesco > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/ARTEMIS-bad-performance-behaviour-after-7-10-days-of-usage- > tp4721272p4721678.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > --001a114c814e4c4e9e0548180a70--