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 Dispatch Router. Once this is successful, my BrokerB will be replaced by something else. Can you please provide a config file that would make this scenario work? Thank you! jjw On Fri, Aug 28, 2015 at 3:10 PM, Ted Ross <[email protected]> wrote: > 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 will fail to open its listener. > > However, simply fixing this problem isn't going to make this work. Can > you provide some more detail as to what you want to see? Are there > specific queues or topics on the brokers that you are using? What is the > desired path for messages to flow along? > > Thanks, > > -Ted > > > > On 08/28/2015 03:00 PM, jjw tectec wrote: > >> 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 5670, and I have a router running the following >> "qdrouterd.conf" config file content: >> >> listener { >> addr: localhost >> port: 5672 >> sasl-mechanisms: ANONYMOUS >> } >> >> connector { >> addr: localhost >> port: 5670 >> sasl-mechanisms: ANONYMOUS >> } >> >> router { >> mode: standalone >> } >> >> Why doesn't the above config work with this simple scenario? >> I tested this broker+router setup using two clients: subscriber >> subscribing >> to port 5670, and publisher publishing to port 5672. Messages don't flow >> through... >> >> Thanks >> >> jjw >> >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
