Uploaded image for project: 'Qpid Dispatch'
  1. Qpid Dispatch
  2. DISPATCH-1474

Console message path skips one router hop

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.9.0
    • Fix Version/s: 1.10.0
    • Component/s: Console
    • Labels:
      None
    • Environment:

      Fedora 29, Firefox 68.0 (64bit), proton 0.29, dispatch current master @2bd50.

       

      Description

      A test has 12 routers, 8 edge and 4 interior spread across two hosts connected by a wireless lan. See attached diagrams.

      The test client on one host sends messages into edge router EA1 and another test client on the other host receives messages from INTD.

      Viewing this with the console and Message path by address turned on the message flow bubbles are visible on only four of the five interrouter hops. Traffic between INTC and INTD never has the traffic flow.

      Other tests show the traffic going all the way through the system correctly. The missing bubbles between INTC and INTD are repeatable. The same test can be restarted and the traffic is missing on that link.

      If traffic enters the system at EC1  (not EA1) then the traffic between INTC and INTD shows as expected.

      Also, router INTD has two edge routers connected to it. In the console app each interior router has an edge bubble labeled "Edge * 2" but the console connection to ED1 shows up as a third Edge bubble. I would expect to have only one bubble labeled "Edge * 2" or two bubbles labeled "Edge".

       

        Attachments

        1. edge2-apr5-network-diagram.pdf
          12 kB
          Charles E. Rolke
        2. dispatch-console-0.9-traffic.png
          80 kB
          Charles E. Rolke

          Activity

            People

            • Assignee:
              eallen Ernest Allen
              Reporter:
              chug Charles E. Rolke
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: