You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@activemq.org> on 2006/03/21 08:36:25 UTC

[jira] Resolved: (AMQ-636) multicast discovery of network connectors can create 2 brokers in 1 JVM if the user changes the brokerName

     [ http://jira.activemq.org/jira//browse/AMQ-636?page=all ]
     
Hiram Chirino resolved AMQ-636:
-------------------------------

    Resolution: Fixed

I made a recent change also that allows the network connector to know which discovered URIs are uris being advertised by the broker, and he will not attempt to establish a connection.

So the ?loopBackMode=true should not be needed anymore.

> 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 RC1

>
>
> 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