On 04/22/2016 10:43 AM, Alexandre Trufanow wrote:
After switching to 0.6-beta2, everything works great!
I did have to patch unit tests to remove ipv6 and sasl/ssl (both are
disabled in my use case). I can provide the modifications I made if you
would like to support this use case.
I have noticed a difference which is probably due to the shift from
fanout=multiple to distribution=balanced. If I have a single producer and 3
receiving brokers, all messages are sent to a single broker (which does not
change between tests). If I have concurrent producers, messages are spread
out but one broker still receives more messages than the rest. Is this
expected behavior? I would expect messages to be spread out more evenly.
There are no clients consuming messages in this use case.
Your original example didn't involve the router in producing messages to
the brokers' exchanges. Are you using autoLink {dir: out...} for
routing deliveries to the routers?
I'm working on some updates to the "balanced" forwarder to make it work
better, but I would still expect that messages from one producer would
be spread across the brokers (unless you are using linkRoute, in which
case each producer is bound at attach-time to a specific broker).
-Ted
Thanks for you help
Alexandre
On Fri, Apr 22, 2016 at 10:33 AM, Alexandre Trufanow <
[email protected]> wrote:
Hi Ted,
I'll look into 0.6.0 beta. The configuration looks much more intuitive, I
am assuming dir: in/out replace phase: 0, 1. Will future versions be
backwards compatible with this configuration?
Thanks!
Alexandre
On Thu, Apr 21, 2016 at 7:22 PM, Ted Ross <[email protected]> wrote:
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
