activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: some broker can't join network of brokers
Date Fri, 09 Jul 2010 09:40:49 GMT
they should have unique names as some if the smarts to suppress
loopbacks depend on unique broker ids

On 9 July 2010 10:22, scow <zkzy2003@hotmail.com> wrote:
>
> b2,b3,b4 have the same broker name 'dynamic-broker1', b1 and b5 get the
> broker name 'dynamic-broker1', if they all use the same broker name, the
> situation is the same, I have test it.
>
> <broker xmlns="http://activemq.apache.org/schema/core"
> brokerName="dynamic-broker2" dataDirectory="${activemq.base}/data">
>
>
>
> Gary Tully wrote:
>>
>> have they all got unique brokerName attributes?
>>
>> On 9 July 2010 09:10, scow <zkzy2003@hotmail.com> wrote:
>>>
>>> I have configured a network of brokers(cluster) use dynamic discovery.
>>> The
>>> typical configuration is
>>>
>>>        <networkConnectors>
>>>          <networkConnector uri="multicast://default?group=com"
>>>            dynamicOnly="true"
>>>            networkTTL="3"
>>>            prefetchSize="1"
>>>            decreaseNetworkConsumerPriority="true" />
>>>        </networkConnectors>
>>>
>>>        <transportConnectors>
>>>            <transportConnector name="openwire" uri="tcp://0.0.0.0:61616"
>>> discoveryUri="multicast://default?group=com" />
>>>        </transportConnectors>
>>>
>>> There are 5 brokers in the cluster. 3 brokers(b2-b4) work well, other
>>> two(b1
>>> and b5) can't join the cluster, they are started like single broker. One
>>> of
>>> them seems can detect other three, it records in log:
>>>
>>>  INFO | Network connection between vm://dynamic-broker2#0 and
>>> tcp://b4/172.28.16.139:61616(dynamic-broker1) has been established.
>>>  INFO | Network connection between vm://dynamic-broker2#2 and
>>> tcp://b2/172.28.16.137:61616(dynamic-broker1) has been established.
>>>  INFO | Network connection between vm://dynamic-broker2#4 and
>>> tcp://b3/172.28.16.138:61616(dynamic-broker1) has been established.
>>>  WARN | Failed to register MBean:
>>> org.apache.activemq:BrokerName=dynamic-broker2,Type=Connection,ConnectorName=openwire,Connection=NC_dynamic-broker1_outbound
>>>  WARN | Failed to register MBean:
>>> org.apache.activemq:BrokerName=dynamic-broker2,Type=Connection,ConnectorName=openwire,Connection=NC_dynamic-broker1_outbound
>>>  INFO | dynamic-broker2 bridge to dynamic-broker1 stopped
>>>  INFO | dynamic-broker2 bridge to dynamic-broker1 stopped
>>>  INFO | Connector vm://dynamic-broker2 Stopped
>>>  INFO | dynamic-broker2 bridge to dynamic-broker1 stopped
>>>
>>> The other one even can't discover other brokers or discovered by others.
>>> All
>>> the 5 brokers are in the same lan and can connect to each other.
>>>
>>> If I configured b1 and b5 with static uri, they can formed a cluster and
>>> work well. Do you have any experience over this situation, thanks.
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://old.nabble.com/some-broker-can%27t-join-network-of-brokers-tp29115245p29115245.html
>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>>
>> --
>> http://blog.garytully.com
>>
>> Open Source Integration
>> http://fusesource.com
>>
>>
>
> --
> View this message in context: http://old.nabble.com/some-broker-can%27t-join-network-of-brokers-tp29115245p29115810.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>



-- 
http://blog.garytully.com

Open Source Integration
http://fusesource.com

Mime
View raw message