So is that one consumer connected to serverA or serverB? Joe
Bas Verhoeven wrote: > > Hello Joe, > > Thanks for the reply. > > > Joe Fernandez wrote: >> >> Try setting dynamicOnly to 'true'. Doing so should preclude the brokers >> from forwarding messages to other brokers that do not have active >> consumers for the target queue. >> > > Am I supposed to set that setting on both servers or just on 'serverA'? I > currently have it set on serverA only and messages are still forwarded to > the other server. If I look at the queues from serverA's webadmin I also > see that there is 1 consumer connected, so ActiveMQ apparently thinks > there is a connection and has no problem forwarding it. However, the only > connections alive at that point are the ServerA <-> ServerB connections. > > It appears that this problem only seems to happen for queues that ServerB > is configured to send back to ServerA. Could this be related? > > Basically the configuration *should* be: > - ServerA should _only_ forward messages sent to 'queue.for.server.b' to > ServerB > - ServerB should _only_ forward messages sent to > 'general.replies.<something>' to ServerA > > The rest of the queues and topics should stay local, and should not be > forwarded over the network. Ever. > > ServerB's config: > > <networkConnectors> > <networkConnector uri="static:(tcp://<snip>:6200)" name="serverA"> > <excludedDestinations> > <queue physicalName=">" /> > <topic physicalName=">" /> > </excludedDestinations> > <staticallyIncludedDestinations> > <queue physicalName="general.replies.>" /> > </staticallyIncludedDestinations> > </networkConnector> > </networkConnectors> > > > -- View this message in context: http://www.nabble.com/ActiveMQ-5.2---Forwarding-only-a-few-queues-to-a-remote-host-tp24790440p24793047.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
