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 On Jan 27, 2016 4:13 PM, "tybreizh29" <mlem...@vecsys.fr> wrote: > Hi Tim, > Thanks a lot for your response. > I was on another project, that's why I was sooo long to answer. > I now understand well that the message is passed from one server to > another. > I have difficulties to put all pieces together. > Unfortunately for me all leads to ActiveMQ FAQ, and i keep confused. > > Right now I'm publishing to cluster1 with stomp (later I will on any > machine) > with java i'm using the failover > (failover:(tcp://msf01.site.com:62616,tcp://msf02.site.com:62616,tcp:// > cluster1.site.com:62616,tcp://amidala.site.com:62616)?timeout=10000'), > so some consumers are reading messages, some are not, because no message is > forwarded) > > I thought the below config should make all messages be forwarded to all > destinations, but not really :( > I'm still stuck :/ > > > <broker xmlns="http://activemq.apache.org/schema/core"; > brokerName="amidala.site.com" dataDirectory="${activemq.data}"> > <networkConnectors> > <networkConnector name="SYSTEM1" duplex="true" > uri="static:(tcp://cluster1.site.com:62616)" userName="system" > password="pass" decreaseNetworkConsumerPriority="true" > > <dynamicallyIncludedDestinations> > <topic physicalName=">" /> > <queue physicalName=">"/> > </dynamicallyIncludedDestinations> > </networkConnector> > <networkConnector name="SYSTEM2" duplex="true" > uri="static:(tcp://amidala.site.com:62616)" userName="system" > password="pass" > > <dynamicallyIncludedDestinations> > <topic physicalName=">"/> > <queue physicalName=">"/> > </dynamicallyIncludedDestinations> > </networkConnector> > <networkConnector name="SYSTEM3" duplex="true" > uri="static:(tcp://msf01.site.com:62616)" userName="system" > password="pass" > > > <dynamicallyIncludedDestinations> > <topic physicalName=">"/> > <queue physicalName=">"/> > </dynamicallyIncludedDestinations> > </networkConnector> > <networkConnector name="SYSTEM4" duplex="true" > uri="static:(tcp://msf02.site.com:62616)" userName="system" > password="pass" > > > <dynamicallyIncludedDestinations> > <topic physicalName=">"/> > <queue physicalName=">"/> > </dynamicallyIncludedDestinations> > </networkConnector> > </networkConnectors> > <transportConnectors> > <transportConnector uri="tcp://cluster1.site.com:62619"/> > <transportConnector uri="tcp://amidala.site.com:62619"/> > <transportConnector uri="tcp://msf01.site.com:62619"/> > <transportConnector uri="tcp://msf02.site.com:62619"/> > </transportConnectors> > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/failover-and-cannot-access-queue-tp4705622p4706506.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
