Re: Problems with ActiveMQ4.1.1 - Master/Slave brokers

[rvenkat23]

Hi

I am also facing the same problem. When the master is killed and slave
becomes the master the messages already placed in the queue are stuck. But
its able to process the new message produced after slave becomes the master. 

We are using ActiveMQ 4.1.1. what am i doing wrong? Can any one post working
master / slave example with configuration please.

Here is our config (shared file system):


 <broker brokerName="broker61650" useJmx="true" persistent="true"
xmlns="http://activemq.org/config/1.0";>

 <persistenceAdapter>
        <journaledJDBC journalLogFiles="5" dataDirectory="/SAN/jms/test/"/>
 </persistenceAdapter>

    <transportConnectors>
       <transportConnector name="openwire" uri="tcp://localhost:61650"/>
    </transportConnectors>
</broker>

Thanks,
Venkatesh.


Cristian3001 wrote:
> 
> I've solved the problem by adding the following to the failover definition
> in my spring configuration files of the listener:
> 
> <property name="brokerURL"
> value="failover:(${host1},${host2})?jms.redeliveryPolicy.allPrefetchValues=${allPrefetchValues}&amp;jms.redeliveryPolicy.initialRedeliveryDelay=${initialRedeliveryDelay}&amp;jms.redeliveryPolicy.maximumRedeliveries=${maximumRedeliveries}&amp;jms.redeliveryPolicy.useCollisionAvoidance=${useCollisionAvoidance}"
> />
> 
> before it was just: 
> 
> <property name="brokerURL" value="failover:(${host1},${host2})" />
> 

-- 
View this message in context: 
http://www.nabble.com/Problems-with-ActiveMQ4.1.1---Master-Slave-brokers-tp10836705s2354p17411749.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.