In a master/slave cluster, only one broker is active at a time; otherwise you have a network of brokers, not master/slave. Does that describe your intended configuration?
If so, what you're seeing indicates that both brokers are active simultaneously. Try to confirm that by hitting both brokers' web consoles; only the master should respond, so if both do then you have a problem. The one thing I know of that can cause a slave broker to become active when it shouldn't is an NFS failure that causes the master to lose the NFS lock on the KahaDB lockfile; see http://activemq.2283324.n4.nabble.com/ActiveMQ-master-slave-topology-issue-BUG-td4695677.html#a4695678 for a detailed description of what can cause that. Does that scenario match your setup? Tim We have two servers where we have two Master(M1, M2)/Slave(S1,S2) setups - M1 is bridged with S2 and M2 with S1; we have also grouped using the multicast protocol; issue here is that in some cases for certain queue, I am setting consumers from the slave to master. is this normal? -- View this message in context: http://activemq.2283324.n4.nabble.com/Consumers-from-SLAVE-tp4702237.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
