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 9625619E54 for ; Fri, 1 Apr 2016 17:31:14 +0000 (UTC) Received: (qmail 42721 invoked by uid 500); 1 Apr 2016 17:31:14 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 42676 invoked by uid 500); 1 Apr 2016 17:31:14 -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 42664 invoked by uid 99); 1 Apr 2016 17:31:13 -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; Fri, 01 Apr 2016 17:31:13 +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 4B2E7C0CD5 for ; Fri, 1 Apr 2016 17:31:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 5.193 X-Spam-Level: ***** X-Spam-Status: No, score=5.193 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_BL_SPAMCOP_NET=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URI_HEX=1.313, URI_TRY_3LD=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id B0mcI538fYe8 for ; Fri, 1 Apr 2016 17:31:10 +0000 (UTC) Received: from mail-yw0-f181.google.com (mail-yw0-f181.google.com [209.85.161.181]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id A5F1A5FB1A for ; Fri, 1 Apr 2016 17:31:10 +0000 (UTC) Received: by mail-yw0-f181.google.com with SMTP id g127so174677658ywf.2 for ; Fri, 01 Apr 2016 10:31:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=pkqXM4gktYkKcJtL2w733MvZUmVVrb9i89RdbpiW0hY=; b=LO77B48qVjPLUu8Je4lyMkW8KbDNT9ABneBYG5nGJh8E41OCau547KiJ+v9iiWrQ06 zDJXtaUvtWf7hkkt3dvpIA4QcLcubXDbsoRWr2c8HME1YFvTjK64PQF0mWY9Rvt9loaX 7NLHTQgRRrs30DvS+chGXPWMWaSk3cIFj7sYpVLfIVC6J24IiHDHCHRM8kRVwYh2lp41 ylAQOeeCOFbwLpS3wfnoF3PmXy4f4Jf+CafkbW0uFduN//cXCVTub5Heu8ojL5kyqCTC Hs+UQ38A9r0WOsv3M4aIw0CfGWqJcgfpftdXX25fylfceXWQtuPCcNydYoRvz9vpocib bCKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=pkqXM4gktYkKcJtL2w733MvZUmVVrb9i89RdbpiW0hY=; b=HFi6J7Vw2+ukpxRD/OQ4h/JIi1Bcp+xGvvLDPsJG0mdTdxT5Q0GBAgZvG0E5KRhEmT r5vmyUm4VPerNyY0VdB17qPPY6Ih2SG86uY/74j1kbhp896ef4yHrSy18Iw0KmvTONF/ Va4NKpYT+r9IKA4/h5Hdhb7U85bvThfIN/6HS89Ie6N9D3Wh1TzukYlo9TVLU72iscGR S8omwoQZGML/0YgJh8+HQXawBK3ABSFG+fIKHhKy59NP8ytOvn3revwDu8427QRx2lhY HokaslYOd3m7W6rylbpkb5DrGSO17OSe6DgT4M6dgoTlheM4HubjfDqRtUOLsS5itTL9 SH6Q== X-Gm-Message-State: AD7BkJJGTygibqadKkBalusLB52Bh3ynZuXNtceyl/VWzGhldIaGWwBilUcvlvktgjOXRxOImWCmUEZahL5rWA== X-Received: by 10.129.33.133 with SMTP id h127mr13259450ywh.169.1459531864630; Fri, 01 Apr 2016 10:31:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.65.17 with HTTP; Fri, 1 Apr 2016 10:30:35 -0700 (PDT) In-Reply-To: <1459521637318-4710199.post@n4.nabble.com> References: <1459493367558-4710175.post@n4.nabble.com> <1459521637318-4710199.post@n4.nabble.com> From: Christopher Shannon Date: Fri, 1 Apr 2016 13:30:35 -0400 Message-ID: Subject: Re: Active MQ 4.1.2 Recovery after persistence database shutdown To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=001a1142926254c016052f6fbe00 --001a1142926254c016052f6fbe00 Content-Type: text/plain; charset=UTF-8 I'm not sure if there has been anything reported that would specifically relate to your issue. So much of the code has changed since then so I wouldn't know what would be related or not at this point. It's also possible that it has been fixed from a side effect of another bug fix or the behavior of the broker changed in such a way that it is no longer a problem. Best the version is so old your best bet would be to try a more recent version to see if there is still a problem. On Fri, Apr 1, 2016 at 10:40 AM, Joel Cambon wrote: > OK, thanks for your answer. I guess I was hoping for too much. But maybe > you > could just tell me if you have had a past bug that needed to be fixed where > messages have been lost? If you could point us to where I could read that > for ActiveMQ 4.1.2 or later, that would be very helpful. I've searched this > information in the list of fixed bugs but I've not found a case matching > our > scenario. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Active-MQ-4-1-2-Recovery-after-persistence-database-shutdown-tp4710175p4710199.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > --001a1142926254c016052f6fbe00--