qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Richardson ...@fourc.eu>
Subject Dispatch router multi-hop topology
Date Tue, 17 Jun 2014 08:59:07 GMT

I'm trying to get an example of a multi-hop topology working with
qpid-dispatch 0.2 built against qpid-proton 0.28. The scenario is probably
most simply described by plagiarising the config files from the
tests/config-3-linear directory, which sets up a series of 3 sequentially
connected routers. From the test topology.txt:
  +----------+          +----------+          +----------+
  |QDR.A     |          |QDR.B     |          |QDR.C     |
  |port:     |          |port:     |          |port:     |
  | 20001    |--------->| 20002    |--------->| 20003    |
  |          |          |          |          |          |
  |          |          |          |          |          |
  +----------+          +----------+          +----------+

 * The direction of the arrow shows the direction of the connection setup
   Connector --> Listener

To each of the config files in this example I've added a listener:

listener {
    port: 5672
    sasl-mechanisms: ANONYMOUS

with the port incremented to 5673 and 5674 in config files B and C (so it
can be run on a single machine).

I'm using drain/spout to send messages with the following syntax:
drain --connection-options {protocol:amqp1.0} -b -f myAddress
spout --connection-options {protocol:amqp1.0} -b myAddress

By varying the port number I can of course control which router the
messages are being sent/received from.

When the drain process connects I can see the mobile address registered on
all three routers. Sending messages via any pair of adjacent routers works
yet I am not able to send an address from router A to router C or visa
versa - spout does not return, presumably since it has not had confirmation
of delivery.

Am I doing something wrong?




*Chris Richardson*, System Architect

*FourC AS, Vestre Rosten 81, Trekanten, NO-7075 Tiller, Norwaywww.fourc.eu

*Follow us on LinkedIn <http://bit.ly/fourcli>, Facebook
<http://bit.ly/fourcfb>, Google+ <http://bit.ly/fourcgp> and Twitter

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message