Is this feature available yet? Thanks,
Gary Tully wrote: > > see the broker waitForSlave option introduced in > https://issues.apache.org/activemq/browse/AMQ-596 > this allows a master to know it is a master and to not accept > connections until a slave has attached. > > it does not fix the problem of replicating old/existing state but it > does allow the situation to be avoided. > > 2008/9/3 Bruce Snyder <[EMAIL PROTECTED]>: >> On Wed, Sep 3, 2008 at 2:55 PM, greenapple <[EMAIL PROTECTED]> wrote: >>> >>> Thanks for your response Bruce, >>> >>> My question is regarding messages that were on the master before the >>> slave >>> connected. Is there a way to sync those? >>> >>> Assume the following: >>> 1. Master starts up >>> 2. Client publish 20 messages >>> 3. Slave starts up >>> 4. Messages from now onwards are replicated >>> >>> My question: is there a way to replicate the messages in (2)? >> >> To my knowledge, that's not possible using master/slave if the >> messages on the master have already been acked to the producer. But >> I'm sure this could be done using Camel to manually replicate any >> pending messages on the master broker to the slave broker. >> >> Bruce >> -- >> perl -e 'print >> unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" >> );' >> >> Apache ActiveMQ - http://activemq.org/ >> Apache Camel - http://activemq.org/camel/ >> Apache ServiceMix - http://servicemix.org/ >> >> Blog: http://bruceblog.org/ >> > > -- View this message in context: http://www.nabble.com/Failover-ActiveMQ-tp19297718p19310834.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
