Oh, Yes, then you are on the right track. ActiveMQ supports 3 models.
Memory (Don't use this) Disk (Use this for speed, niceness and whatnot else) JDBC (It'll be slow) /je On May 11, 2011, at 11:06 PM, archa wrote: > My requirement is as follows: > > I have my application which currently write to a single broker queue. > Incase the broker goes down, my messages are lost, till I restart the broker > and the consumers again (as consumers are formed on application startup). > > To avoid the loss of messages, I want sort of a master-slave configuration, > so that when the master goes down, the slave broker continues consuming the > messages, without requiring the message producer to change the broker ip in > its configuration. > > I read about master-slave configuration in > http://activemq.apache.org/jdbc-master-slave.html . Here it mentions about > failover, but how is the failover mentioned in the activemq.xml (cant see it > in the example given in that url). Also, will the failover be same for the > master and slave, as it is a cluster ? > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Native-Clustering-in-ActiveMQ-tp3516488p3516511.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
