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 9F11F18693 for ; Mon, 11 Jan 2016 21:23:57 +0000 (UTC) Received: (qmail 67129 invoked by uid 500); 11 Jan 2016 21:23:57 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 67079 invoked by uid 500); 11 Jan 2016 21:23:57 -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 67063 invoked by uid 99); 11 Jan 2016 21:23:56 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jan 2016 21:23:56 +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 7F3AEC05A2 for ; Mon, 11 Jan 2016 21:23:56 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.565 X-Spam-Level: **** X-Spam-Status: No, score=4.565 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, URIBL_BLOCKED=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 mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id p78SwQ6Av_co for ; Mon, 11 Jan 2016 21:23:44 +0000 (UTC) Received: from mail-io0-f170.google.com (mail-io0-f170.google.com [209.85.223.170]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 4DB5031AC9 for ; Mon, 11 Jan 2016 21:23:43 +0000 (UTC) Received: by mail-io0-f170.google.com with SMTP id g73so166832768ioe.3 for ; Mon, 11 Jan 2016 13:23:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=pLuCJNlnrCNNurySpfZD5d6NkwbTxW0ug+thNGNuE88=; b=gcuGN68RtDEKP2xuBNDBj1KMC9I16E01XgXWyaEyz1FeQtNZrLAmHpOymT1Nowh2aO eaqfnON36g9ab3Sc9K2I5121BkmyBwSjCtrUrAZS3vxs9GAg9HTRjyAisbfZoumx64xJ vtGF7NOklK0cSj9pxHPWG9l4gH6xpH2P05bTEdhOg4+XEifFKXxAlqeGQU2oYUHY4uVy /tAiQaOr81uKlTUNX897bomszSu01Kh+JkIAiE3fBQrCjh59f3o4GnP7e15sYp5oJYgQ sYLXh0cjWS7IkFu4GH9PZFGPRG/ghlWaHy3X+b18Js45z4nE0+RavefApw3h4z2fdguz x2Ow== MIME-Version: 1.0 X-Received: by 10.107.128.206 with SMTP id k75mr66417924ioi.76.1452547422287; Mon, 11 Jan 2016 13:23:42 -0800 (PST) Sender: tbain98@gmail.com Received: by 10.50.249.42 with HTTP; Mon, 11 Jan 2016 13:23:42 -0800 (PST) Received: by 10.50.249.42 with HTTP; Mon, 11 Jan 2016 13:23:42 -0800 (PST) In-Reply-To: <1452467768227-4705735.post@n4.nabble.com> References: <1452419215234-4705730.post@n4.nabble.com> <1452421419884-4705731.post@n4.nabble.com> <1452467232038-4705733.post@n4.nabble.com> <1452467768227-4705735.post@n4.nabble.com> Date: Mon, 11 Jan 2016 14:23:42 -0700 X-Google-Sender-Auth: iAEcGTScyiMrlMHXDR2b10bZT_A Message-ID: Subject: Re: Message stuck after failover [5.11.1, 5.13.0] From: Tim Bain To: ActiveMQ Users Content-Type: multipart/alternative; boundary=001a113f99301ffd230529158de6 --001a113f99301ffd230529158de6 Content-Type: text/plain; charset=UTF-8 If there's no shared store, you can failover between the two for new messages, but any messages in the persistence store of the broker will be unavailable while it's down and only be dispatched once it comes back up. Which sounds like exactly what you're seeing. If you want redundancy, make them a master/slave pair. Tim On Jan 11, 2016 10:10 AM, "yang.yang.zz" wrote: > Thanks for replay Tim! I've posted the two config files above. For your > questions: > > > /Are broker2a and broker2b configured as a master/slave pair with a shared > persistence store, or simply as two standalone brokers? If there is a > shared persistence store, which type is it? / > > There's no special setting on broker2a and broker2b. They are just using > TransportConnectors which allows broker1's network connector connecting to > it. There's no shared persistent store. They are two standalone brokers > serves as a failover backup to each other. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Message-stuck-after-failover-5-11-1-5-13-0-tp4705730p4705735.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > --001a113f99301ffd230529158de6--