Hi Alexandre,
Could I get you to try the qpid-dispatch 0.6.0 beta?
(https://cwiki.apache.org/confluence/display/qpid/What's+New+in+Apache+Qpid+Dispatch+Router+0.6.0)
Your use case is greatly improved in this new version. I just verified
your use case with the following configuration fragment:
connector {
addr: <broker-host>
port: <broker-port>
role: route-container
name: BrokerA
}
address {
prefix: queue
waypoint: yes
}
autoLink {
addr: queue
dir: in
connection: BrokerA
}
The "connector" causes the router to establish a connection to the
broker with the exchange and queue. The "address" establishes the
namespace starting with "queue" as being a waypoint address (i.e. on a
broker). The "autoLink" instructs the router to subscribe to the queue
on BrokerA once the connection is opened. This subscription will then
feed deliveries to mobile consumers on address "queue".
You can then scale it out by adding an instance of "connector" for each
additional broker and an instance of "autoLink" for the queue on the broker:
connector {
addr: <broker-b-host>
port: <broker-b-port>
role: route-container
name: BrokerB
}
autoLink {
addr: queue
dir: in
connection: BrokerB
}
Regards,
-Ted
On 04/21/2016 12:03 PM, Alexandre Trufanow wrote:
Hi all,
I am trying to get the following working on dispatch-0.5:
producer -> brokerA.exchange -> brokerA.queue -> dispatcher -> consumer
Subscribing a consumer to the queue directly on the broker works fine but I
haven't managed to find a configuration where a mobile subscriber on the
dispatcher can receive messages.
Is there a sample configuration somewhere for mobile consumers connecting
to a dispatcher ? Ideally I would like to be able to add multiple brokers
with the same queue name to be able to scale.
Thanks,
Alexandre
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
