Return-Path: Delivered-To: apmail-geronimo-activemq-dev-archive@www.apache.org Received: (qmail 62800 invoked from network); 16 Mar 2006 15:46:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Mar 2006 15:46:13 -0000 Received: (qmail 74368 invoked by uid 500); 16 Mar 2006 15:46:13 -0000 Delivered-To: apmail-geronimo-activemq-dev-archive@geronimo.apache.org Received: (qmail 74337 invoked by uid 500); 16 Mar 2006 15:46:13 -0000 Mailing-List: contact activemq-dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-dev@geronimo.apache.org Delivered-To: mailing list activemq-dev@geronimo.apache.org Delivered-To: moderator for activemq-dev@geronimo.apache.org Received: (qmail 59074 invoked by uid 99); 16 Mar 2006 10:34:40 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Message-ID: <19839876.1142512585970.JavaMail.tomcat@stilton> Date: Thu, 16 Mar 2006 04:36:25 -0800 (PST) From: "james strachan (JIRA)" To: activemq-dev@geronimo.apache.org Subject: [jira] Created: (AMQ-636) multicast discovery of network connectors can create 2 brokers in 1 JVM if the user changes the brokerName MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at goku.simulalabs.com X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N multicast discovery of network connectors can create 2 brokers in 1 JVM if the user changes the brokerName ---------------------------------------------------------------------------------------------------------- Key: AMQ-636 URL: http://jira.activemq.org/jira//browse/AMQ-636 Project: ActiveMQ Type: Improvement Reporter: james strachan Fix For: 4.0 M5 Someone reported on IRC yesterday. The issue was the multicast discovery sending out a request, which happened to contain a broker name different to the one configured via XML. To fix this we could consider enabling loopBackMode by default for multicast transport and multicast discovery -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.activemq.org/jira//secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira