Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 32748D599 for ; Mon, 15 Oct 2012 20:43:04 +0000 (UTC) Received: (qmail 22897 invoked by uid 500); 15 Oct 2012 20:43:03 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 22829 invoked by uid 500); 15 Oct 2012 20:43:03 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 22737 invoked by uid 99); 15 Oct 2012 20:43:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Oct 2012 20:43:03 +0000 Date: Mon, 15 Oct 2012 20:43:03 +0000 (UTC) From: "Andrew Cohen (JIRA)" To: dev@activemq.apache.org Message-ID: <563175837.47333.1350333783771.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (AMQ-4108) Cannot recieve 'ActiveMQ.Advisory.MasterBroker' messages when master dies and slave takes control MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Andrew Cohen created AMQ-4108: --------------------------------- Summary: Cannot recieve 'ActiveMQ.Advisory.MasterBroker' messages when master dies and slave takes control Key: AMQ-4108 URL: https://issues.apache.org/jira/browse/AMQ-4108 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.7.0 Environment: Windows or Linux. Java 1.7.0_07. Reporter: Andrew Cohen Message consumers do not receive 'ActiveMQ.Advisory.MasterBroker' advisory messages when the master is killed and the slave takes over. Steps: 1) Start Master and Slave brokers in Pure "Master / Slave" Configuration. 2) Create a client consumer for the 'ActiveMQ.Advisory.MasterBroker' topic. (See code below) 3) Kill the Master broker. (kill -9) 4) The client will failover to the slave. Note the Web Console shows there is one en-queued message for the 'ActiveMQ.Advisory.MasterBroker' topic. 5) The consumer will never receive/dequeue this message. (Event after restarting the client) Two other observations: 1) Other advisories (such as the 'ActiveMQ.Advisory.Connection')are working. This only seems to be a problem with 'ActiveMQ.Advisory.MasterBroker'. 2) Sending a message to the 'ActiveMQ.Advisory.MasterBroker' via the Web Console is properly received and dequeued by the consumer. Code: Session session = conn.createSession(false, Session.AUTO_ACKNOWLEDGE); MessageConsumer consumer = session.createConsumer( AdvisorySupport.getMasterBrokerAdvisoryTopic() ); // It will receive Connection Advisory messages! Just not MasterBroker advisory messages :( //MessageConsumer consumer = session.createConsumer( AdvisorySupport.getConnectionAdvisoryTopic() ); Message msg = null; while (true) { // Also doesn't work with MessageListener implementation msg = consumer.receive(30000); System.out.println(name + " Received: " + msg); } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira