activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From SuoNayi <suonayi2...@163.com>
Subject Reply:network of broker - update and rebalance not working
Date Tue, 31 Jan 2012 15:35:47 GMT
Seems the same trouble I got into some days ago.
What I want brokers to do is to update clients with urls of brokers of joining or leaving
the cluster,
and rebalance clients for us too.
I set up two networked brokers and follow a instruction in a blog(cannot remember the url)
with setting three properties of transport to be true.
The result of test shows this function does not work well and I have raised a jira.
see https://issues.apache.org/jira/browse/AMQ-3544.

At 2012-01-31 17:15:12,tomerb <tomerb@waze.com> wrote:
>Hi
>I'm having trouble making the *updateClusterClients="true"
>rebalanceClusterClients="true"* work
>I have a network of brokers size 2 with the following brokers configuration
>
>*<beans
>  xmlns="http://www.springframework.org/schema/beans"
>  xmlns:amq="http://activemq.apache.org/schema/core"
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>  xsi:schemaLocation="http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
>  http://activemq.apache.org/schema/core
>http://activemq.apache.org/schema/core/activemq-core.xsd">
>
>    
>    <bean
>class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
>        <property name="locations">
>            <value>file:${activemq.base}/conf/credentials.properties</value>
>        </property>      
>    </bean>
>
>    
>    <broker xmlns="http://activemq.apache.org/schema/core"
>brokerName="localhost" dataDirectory="${activemq.base}/data"
>destroyApplicationContextOnStop="true" persistent="false">
> 
>        
>
>              
>        <destinationPolicy>
>            <policyMap>
>              <policyEntries>
>                <policyEntry topic=">" producerFlowControl="true"
>memoryLimit="5mb">
>                  <pendingSubscriberPolicy>
>                    <vmCursor />
>                  </pendingSubscriberPolicy>
>                </policyEntry>
>                <policyEntry queue=">" producerFlowControl="true"
>memoryLimit="50mb">
>
>                  
>                </policyEntry>
>              </policyEntries>
>            </policyMap>
>        </destinationPolicy> 
>        
>        
>        <managementContext>
>            <managementContext createConnector="false"/>
>        </managementContext>
>
>        <networkConnectors>
>            <networkConnector name="tomer1"
>uri="static:(tcp://tomer-amq-test1:61616)"/>
>        </networkConnectors>
>
>        
>        <persistenceAdapter>
>           <memoryPersistenceAdapter/>
>        </persistenceAdapter>
>        
>        
>          
>
>		  
>        
>        <transportConnectors>
>            <transportConnector name="openwire" uri="tcp://0.0.0.0:61616"
>updateClusterClients="true" rebalanceClusterClients="true" />
>        </transportConnectors>
>
>    </broker>
>
>    
>    <import resource="jetty.xml"/>
>    
></beans>*
>
>
>the client is running
>*ant consumer -Dmax=999999 -Durl=failover:\(tcp://tomer-amq-test2:61616\) *
>
>the client always connect only to the specified broker (tomer-amq-test2)
>and when I stop or start the second broker, there is no recconection from
>the client
>and if I stop the specified broker, there is no connection made by the
>client to the second server
>
>otherwise the cluster works as expected
>can someone help please?
>am I missing something?
>
>Tx Tomer
>
>
>--
>View this message in context: http://activemq.2283324.n4.nabble.com/network-of-broker-update-and-rebalance-not-working-tp4343907p4343907.html
>Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message