How did you setup failover? Did you test that the brokers actually lock on either a file/memory/db-table?
Visually - the DB setup is the easiest to see, you'll see a table lock in effect on the slave broker and that it is not starting. Are you possibly confusing persistence with HA? The two while useful together are not the same. I.e 1 : - You want to test and setup Master/Slave 2 : - You want to investigate persistence, - this is not clustering, it is per broker save to a media. Then you want to match this to your client / usage topology and see if it is enough to meet your needs. If it is not and you want more "brokers" you want to look at a network of brokers. /je On Sep 14, 2010, at 11:01 PM, activeMqUser wrote: > > Hi Johan, > > i have set up the clients for fail over as i mentioned in the previous posts > even though i am not sure if i have done it correctly as i am very much a > new user of ActiveMQ. I have posted the network configuration info and some > log info also which shows the Main Broker is successfully connecting to one > of other two Broker on start up and the bridge is successfully established > between the Brokers in my previous request. Is there anything else i need to > do? If yes please let me know about that. > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Failover-problem-tp2537292p2539947.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. Johan Edstrom j...@opennms.org They that can give up essential liberty to purchase a little temporary safety, deserve neither liberty nor safety. Benjamin Franklin, Historical Review of Pennsylvania, 1759
