On Wed, Jul 25, 2018 at 5:48 AM, VERMEULEN Olivier <olivier.vermeu...@murex.com> wrote: > Hello > > Thanks for your replies > > @Ganesh, I'm trying to setup the same use case with a more recent > dispatch-router (1.0.0) but so far I can't even make the dispatch-router > work. My autolinks are in failed state with the following error: "received > Attach with remote null terminus". Do you have an idea? > > @Ted, shouldn't the configuration be symmetric? If for example I have 3 > dispatch-routers (A, B, C) with A having connectors on B and C and the other > two having a listener, what happens if A crashes? B and C won't be able to > communicate no?
You can set up a full mesh of the three routers by adding a connector from B to C. A two-router mesh requires one connector; A three-router mesh requires three connectors (one for each edge in the graph). Having two inter-router connections between any pair of routers is a misconfiguration. > > Thanks, > Olivier > > -----Original Message----- > From: Ted Ross <tr...@redhat.com> > Sent: lundi 23 juillet 2018 18:20 > To: users@qpid.apache.org > Subject: Re: Inter-connected dispatch-routers > > Unrelated to your symptom, there is a misconfiguration in your setup. > You have two inter-router connections between your routers, one established > in each direction (i.e. each router has an inter-router listener _and_ > connector). You only need one inter-router connection. > > -Ted > > On Mon, Jul 23, 2018 at 10:18 AM, VERMEULEN Olivier > <olivier.vermeu...@murex.com> wrote: >> Hello, >> >> I started 2 Dispatch-Routers (version 0.7.0) and 1 Broker-J (version >> 7.0.3) My first Dispatch-Router has an out autolink on a topic: >> >> router { >> id: router.10104 >> mode: interior >> worker-threads: 4 >> } >> listener { >> host : 0.0.0.0 >> port: 10104 >> role: normal >> authenticatePeer: no >> } >> listener { >> host : 0.0.0.0 >> port: 10204 >> role: inter-router >> authenticatePeer: no >> } >> connector { >> name: router.10205 >> host: dell440srv >> port: 10205 >> role: inter-router >> } >> address { >> prefix: myTopic >> waypoint: yes >> } >> address { >> prefix: myQueue >> waypoint: yes >> } >> connector { >> name: broker.5673 >> host: dell440srv >> port: 5673 >> role: route-container >> } >> autoLink { >> name: broker.5673.myTopic >> addr: myTopic >> connection: broker.5673 >> dir: out >> } >> >> My second Dispatch-Router has an in autolink on a queue bound to the >> previous topic: >> >> router { >> id: router.10105 >> mode: interior >> worker-threads: 4 >> } >> listener { >> host : 0.0.0.0 >> port: 10105 >> role: normal >> authenticatePeer: no >> } >> listener { >> host : 0.0.0.0 >> port: 10205 >> role: inter-router >> authenticatePeer: no >> } >> connector { >> name: router.10204 >> host: dell440srv >> port: 10204 >> role: inter-router >> } >> address { >> prefix: myTopic >> waypoint: yes >> } >> address { >> prefix: myQueue >> waypoint: yes >> } >> connector { >> name: broker.5673 >> host: dell440srv >> port: 5673 >> role: route-container >> } >> autoLink { >> name: broker.5673.myQueue >> addr: myQueue >> connection: broker.5673 >> dir: in >> } >> >> Both Dispatch-Routers are inter-connected. >> Now when I connect to the second dispatch-router I can send and receive >> messages. >> But when I connect to the first one, I can only send... the receive does not >> find anything... >> Did I miss something in the configuration? >> >> Thanks, >> Olivier >> >> ******************************* >> >> This e-mail contains information for the intended recipient only. It may >> contain proprietary material or confidential information. If you are not the >> intended recipient you are not authorised to distribute, copy or use this >> e-mail or any attachment to it. Murex cannot guarantee that it is virus free >> and accepts no responsibility for any loss or damage arising from its use. >> If you have received this e-mail in error please notify immediately the >> sender and delete the original email received, any attachments and all >> copies from your system. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional > commands, e-mail: users-h...@qpid.apache.org > > ******************************* > > This e-mail contains information for the intended recipient only. It may > contain proprietary material or confidential information. If you are not the > intended recipient you are not authorised to distribute, copy or use this > e-mail or any attachment to it. Murex cannot guarantee that it is virus free > and accepts no responsibility for any loss or damage arising from its use. If > you have received this e-mail in error please notify immediately the sender > and delete the original email received, any attachments and all copies from > your system. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org