Hi Tim
yes i'm having the same config (except the broker name change).
when you say not not send to itself you mean for example system write :
<dynamicallyIncludedDestinations>
<topic physicalName="outgoing.System2" />
<topic physicalName="outgoing.System3" />
<topic physicalName="outgoing.System4" />
</dynamicallyIncludedDestinations>
Regarding what happened:
I've posted some message to cluster1, i saw some of those messages on amidala,
some have been dequeued from cluster1. i did not see any message arriving on
msf01 or msf02.
I'm unable to dequeue the messages on amidala from any other server, they
remain there.
marc
Le 28/01/2016 06:28, Tim Bain [via ActiveMQ] a écrit :
Are you using this config file for all four brokers? It looks like you're
having each broker connect not only to the other three but also to itself;
is that true? If so, I'm not sure what happens if a broker connects to
itself, but I'd try eliminating that from the configuration and see if it
changes anything.
Also, are you getting zero messages forwarded, or some but not all? And is
the problem that some messages can't be consumed because there is no
consumer on the broker on which they're published, or just that that local
consumers are taking all the messages so consumers on the other brokers
never get any? If you could describe what you expect to happen and what's
actually happening in more detail (including information like which
producers and consumers are on which brokers), that may make it faster and
easier to help you figure out what's going on.
Tim
--
View this message in context:
http://activemq.2283324.n4.nabble.com/failover-and-cannot-access-queue-tp4705622p4706563.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
