Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Date: Sun, 10 Jan 2016 02:23:39 -0800 (PST)
From: "yang.yang.zz" <yang.yang.zz@outlook.com>
To: users@activemq.apache.org
Message-ID: <1452421419884-4705731.post@n4.nabble.com>
In-Reply-To: <1452419215234-4705730.post@n4.nabble.com>
References: <1452419215234-4705730.post@n4.nabble.com>
Subject: Re: Message stuck after failover [5.11.1, 5.13.0]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I was trying to imagine what's happening behind the scenes....

*before failover*

                       B1 (up)
                     / 
A --- failover ?  
                     \
                       B2 (down)

*after failover*

                       B1 (down)
                     / 
A --- failover ?  
                     \
                       B2 (up)


After failover, A can still send message to B2. So, to this point, this
failover went succeed. But B2, as a backup broker and producer, couldn't
send message to A. All the messages from B2 are stuck at B2's local broker.

However, restarting the broker at A will solve it. So it seems to be
restarting A broker will re-register consumer listeners at A. So it will
consume messages queued at B? Shouldn't the failover does the
re-registration automatically? Does A's broker have to be restarted after
the failover??


--
View this message in context: http://activemq.2283324.n4.nabble.com/Message-stuck-after-failover-5-11-1-5-13-0-tp4705730p4705731.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.