activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mserrano <>
Subject in master slave broker network, networked slave incorrectly bound to other slave
Date Tue, 06 Nov 2012 19:32:15 GMT
Sorry if the phrasing of this topic is awkward -- this is difficult to

I am running networked master/slave brokers.  That is I have two shared
nothing master/slave broker setups which are networked together.  When the
masters both shutdown or fail, I am seeing one slave create a MasterBroker
filter for the slave it is /networked/ to.  This is evidenced by the
following log messages:

from slave2 log, connecting slave1 as a slave!

first log message is my own i added to help diagnose the issue.

I have captured the stack trace when this occurs, where you can see the it
is processing a remote command coming in over the network bridge.  I would
think that it should never treat this as a real slave since it is a
networked broker.  Notice however (from above logs) that it is not marked as

Any ideas?  Am I misunderstanding what is going on?  I have seen subsequent
shutdown problems where slave2 is stuck trying to copy a command to slave1,
which is what led me to track this down to this point.

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message