Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5E2DB1822F for ; Mon, 22 Jun 2015 13:18:20 +0000 (UTC) Received: (qmail 4550 invoked by uid 500); 22 Jun 2015 13:18:19 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 4510 invoked by uid 500); 22 Jun 2015 13:18:19 -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 4498 invoked by uid 99); 22 Jun 2015 13:18:19 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jun 2015 13:18:19 +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 160A8CF744 for ; Mon, 22 Jun 2015 13:18:19 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.564 X-Spam-Level: **** X-Spam-Status: No, score=4.564 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_TRY_3LD=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id FGxQa5yIiN9X for ; Mon, 22 Jun 2015 13:18:13 +0000 (UTC) Received: from mail-ie0-f171.google.com (mail-ie0-f171.google.com [209.85.223.171]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 08CB821F26 for ; Mon, 22 Jun 2015 13:18:13 +0000 (UTC) Received: by iebrt9 with SMTP id rt9so3593070ieb.2 for ; Mon, 22 Jun 2015 06:18:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=9v2jWyS6pKVhGJ6SiyNsc2MbQmk4z4zvrqJ0RQByUaw=; b=lkaftuthPRyilm+KHUKbZ9WdZUP098sWLYcrDN8BMSObx2nuFKOsSTK9pZPd+78RpH +p9MAmNXXUpCnKKNQyJiP2jiisaRsYeXJdkEf7JtjTtvq/zATpvrjbW6/V4GS8AazW3l cA3Lc0K/69Wy8XTXyDKX0oy57kVy6c6nV0lF0BzKAklX4XQa0QMRajrtLM3mFYlZzm0v voPrIQLNphT2xtPvn15hl/AoFn7/nRk8LwCR8wTm0CK9yvgRoF5Y8qauriZiGinHBD59 SqCVFHcsI+lZhn6WTPLY06aNmD2L/MNb31WDhfoOJ0k29aPu0cG+ZanENSUOhhJBYXop DpZQ== X-Received: by 10.43.17.135 with SMTP id qc7mr25797735icb.14.1434979092550; Mon, 22 Jun 2015 06:18:12 -0700 (PDT) MIME-Version: 1.0 Sender: tbain98@gmail.com Received: by 10.50.251.141 with HTTP; Mon, 22 Jun 2015 06:17:52 -0700 (PDT) In-Reply-To: References: <1434956579658-4698038.post@n4.nabble.com> From: Tim Bain Date: Mon, 22 Jun 2015 07:17:52 -0600 X-Google-Sender-Auth: x_CnWj7hx9qwjntRthC3X93M684 Message-ID: Subject: Re: ActiveMQ does not keep durable subscription when re-start To: ActiveMQ Users Content-Type: multipart/alternative; boundary=bcaec51822b41258ea05191b1bc6 --bcaec51822b41258ea05191b1bc6 Content-Type: text/plain; charset=UTF-8 I agree with Tim: you haven't provided enough details about your configuration and your test case when asking for help. (The same was true for your issue that turned out to be the RETAINED flag; knowing how many and which messages were being re-delivered might have made it easier to zero in on the problem quicker.) So please tell us: - How you've configured the broker's persistence store - Whether you've configured any other broker options that you think might be relevant (the easiest way to do this is just publish your broker config file) - How you're creating the durable subscribers (last time you were using the web console; from your description I wasn't sure if the MQTT subscriber was doing that in code) - How you're determining that the durable subscription has been deleted (have you looked in JMX, or just the web console, or are you determining based whether the subscriber gets more messages?) - What the behavior of the subscriber is at the time you restart the broker (have you stopped it or is it still running? does it successfully reconnect, or not? does a new subscription get created when it reconnects? what else are you seeing that you think would be useful to us?) Tim, the other question targeted 5.11.1, so I'd guess the same is true here. But SummerScent, it's always good practice to make threads stand on their own without relying on someone having read the prior ones, because anyone who gets here by searching Google for a related problem isn't going to read the earlier threads. Tim On Mon, Jun 22, 2015 at 6:33 AM, Timothy Bish wrote: > The durable subscription functionality is pretty well tested at this point > so I'd be more inclined to suspect configuration problems. You haven't set > something like delete all messages on start or something in your ActiveMQ > configuration. > > Its a good idea to provide version information and even better test cases > or sample code for questions like this so we can see what is going on. > > On Mon, Jun 22, 2015 at 3:02 AM, SummerScent > wrote: > > > Hi all, > > > > I have a MQTT subscriber which create some Durable Topic Subscribers when > > connected to ActiveMQ. > > > > But when the ActiveMQ restarts, it clear all the Durable Topic > Subscribers. > > > > Do you have any solution to keep these Durable Topic Subscribers even > when > > the ActiveMQ restart? > > > > Thank you! > > > > > > > > > > > > -- > > View this message in context: > > > http://activemq.2283324.n4.nabble.com/ActiveMQ-does-not-keep-durable-subscription-when-re-start-tp4698038.html > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > > > > > -- > -- > Tim Bish > --bcaec51822b41258ea05191b1bc6--