I am bootstrapping my dispatch router knowledge on a little project driven by the need to feed messages through:
- AMQP 0-10 client sends messages to a broker that speaks both 0-10 and 1.0 - dispatch router takes messages out of that dual-protocol broker and routes them to another broker that speaks only 1.0 ... and back the other way, with a different named queue. So here is the qdrouterd.conf pieces for this goal: router { mode: standalone id: Router.A } #Listener for the dispatch-router management connections - qdstat listener { host: 0.0.0.0 port: amqp authenticatePeer: no } connector { name: otherbroker host: otherhost port: 5672 role: route-container } connector { name: appbroker host: 0.0.0.0 port: 10053 role: route-container } address { prefix: to.myapp waypoint: yes } autoLink { addr: to.myapp connection: appbroker dir: in } autoLink { addr: to.myapp connection: otherbroker dir: out } address { prefix: from.myapp waypoint: yes } autoLink { addr: from.myapp connection: appbroker dir: out } autoLink { addr: from.myapp connection: otherbroker dir: in } When qdrouterd runs, it appears to set up the connections and links, but no messages are retrieved from 'appbroker' 'to.myapp' - and there are many messages sitting in that queue waiting. Is there something I'm missing to actually get the messages to flow? Thanks, -Steve --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org