I'm seeing some strange behavior with ActiveMQ 5.4.2 pure master slave setup...
5.4.2 master running on mqmaster01: <broker xmlns="http://activemq.apache.org/schema/core" brokerName="localhost" dataDirectory="${activemq.base}/data" destroyApplicationContextOnStop="true" schedulerSupport="false" advisorySupport="false"> ... <transportConnectors> <transportConnector name="openwire" uri="tcp://0.0.0.0:61616"/> </transportConnectors> 5.4.2 slave running on mqslave01: <broker masterConnectorURI="tcp://mqmaster01:61616" shutdownOnMasterFailure= "false" xmlns="http://activemq.apache.org/schema/core" brokerName="localhost" da taDirectory="${activemq.base}/data" destroyApplicationContextOnStop="true" sched ulerSupport="false" advisorySupport="false"> ... <transportConnectors> <transportConnector name="openwire" uri="tcp://0.0.0.0:61616"/> </transportConnectors> Producers and consumers are using this connection URL: failover:(tcp://mqmaster01:61616,tcp://mqslave01:61616)?randomize=false Here's what I'm seeing. I start up the master. My producers/consumers connect immediately (they were waiting to connect) and begin doing their thing. I then start up the slave (with a freshly emptied ./data dir). The slave connects to the master, as witnessed by this in data/activemq.log on mqslave01: 2011-08-24 22:51:48,833 | INFO | Starting a slave connection between vm://localhost#0 and tcp://mqmaster01:61616 | org.apache.activemq.broker.ft.MasterConnector | main 2011-08-24 22:51:48,843 | INFO | Slave connection between vm://localhost#0 and tcp://mqmaster01/10.0.3.42:61616 has been established. | org.apache.activemq.broker.ft.MasterConnector | main Shortly thereafter, a message is sent to a queue. A consumer consumes it. On mqmaster01, I can see on http://mqmaster01:8161/admin/queues.jsp that the enqueue/dequeue count went up by one, and "Number Of Pending Messages" is zero. All good, right? Yeah, except mqslave01 now shows Messages Enqueued = 1, and Number Of Pending Messages = 1. As more messages run through the system, mqslave01's enqueue & pending count continues to go up, but the dequeue count remains at zero. I don't understand why the slave isn't replicating the consumption of these messages... Has anybody seen this before? Any idea what might be causing it? Did I screw something up in my configuration, i.e. with schedulerSupport="false" or advisorySupport="false"? Any help would be much appreciated... ----- Dan Checkoway dcheckoway gmail com -- View this message in context: http://activemq.2283324.n4.nabble.com/Slave-not-replicating-consumption-with-Pure-Master-Slave-tp3767086p3767086.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.