Thanks for the clarification. There's a feature that's not yet
implemented that would be a very good solution to your test case. If
the router network could set up a link from amq.topic on BrokerA to
amq.topic on BrokerB, you would get reliable transfer of messages from
broker to broker. By
In this simple test, I'm having clients publishing/subscribing to amq.topic:
qpid-receive -b localhost:5670 -a amq.topic -f
qpid-send -b localhost:5672 -a amq.topic -m 1 --content-string "hello"
If Dispatch works, then in the future we plan to replace BrokerB with
Microsoft Azure Service Bus.
Th
On 08/28/2015 04:42 PM, Ted Ross wrote:
What are you using the brokers for in this scenario? Will you be
replacing BrokerB with another messaging intermediary or some consuming
process?
I'm asking because your description says nothing about the configuration
of the brokers (besides the ports
What are you using the brokers for in this scenario? Will you be
replacing BrokerB with another messaging intermediary or some consuming
process?
I'm asking because your description says nothing about the configuration
of the brokers (besides the ports used). Are you using queues and/or
top
Hi Ted,
My 2nd broker is running on a different port 5670 (command: ./qpidd -p 5670
--data-dir /home/mmos/datadir/).
So the scenario I'm trying to test is the following:
Client_publisher -> BrokerA (port 5672) -> Router -> BrokerB (port 5670) ->
Client_subscriber
This is my first step in testing
Hi,
Thanks for giving Dispatch Router a try. I'm a little unclear as to
exactly what it is you are trying to do.
It looks to me that you have both BrokerA and the Router listening on
port 5672. This is not going to work as whichever process you start
first will get the port and the other w
Hello,
I'm trying to run a quick test using Dispatch Router, and I think I need
help with configuration.
I'd like to set up such a router between two AMQP brokers, and routes
messages from BrokerA to BrokerB.
Right now, I have Qpid BrokerA running on port 5672, and Qpid BrokerB
running on port 5
