Attach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 5.2.0
    • 5.3.0
    • Connector
    • None
    • Patch Available

    Description

      Multicast discovery does not work properly on multihomed Windows 2003
      Packets are sent to unpredictable network interface that results in brokers loosing connection with each other.
      It would be nice to be able to specify network interface for multicast socket right in the discovery URI.

      So transport connection definition turns from

              <transportConnectors>
                  <transportConnector name="openwire" uri="tcp://0.0.0.0:61617" discoveryUri="multicast://224.0.0.1"/>
             </transportConnectors>
      

      to

              <transportConnectors>
                  <transportConnector name="openwire" uri="tcp://0.0.0.0:61617" discoveryUri="multicast://224.0.0.1?networkInterface=eth0"/>
             </transportConnectors>
      

      I added support for interface/networkInterface for multicast on multihomed hosts. See attached patch

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            gtully Gary Tully
            ikatkov Igor Katkov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment