Uploaded image for project: 'FUSE Message Broker'
  1. FUSE Message Broker
  2. MB-1129

Duplex option on Network Connector not supported

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 5.5.1-fuse-03-06
    • Fix Version/s: 5.5.1-fuse-04-01
    • Component/s: None
    • Labels:
      None
    • Environment:

      Fuse Message Broker 5.5.1-fuse-03-06
      Fuse Message Broker 5.3.0.4

      Description

      It has been reported and confirmed with testing that when configuring a NetworkConnector as follows messages are not forwarded across the bridge. The scenario for this test case is as follows:

      NetworkConnector configured on 5.5.1-fuse-03-06

      <networkConnector uri="static:(failover:(tcp://localhost:61616,tcp://localhost:62616))?maxReconnectAttempts=1000;useExponentialBackOff=false;maxReconnectDelay=30000"
                             name="bridge"
                             networkTTL="6"
                             duplex="true"
                             dynamicOnly="false"
                             conduitSubscriptions="true"
                             decreaseNetworkConsumerPriority="false">
                      <excludedDestinations>
                      </excludedDestinations>
                      <dynamicallyIncludedDestinations>
                         <topic physicalName="TEST"/>
                      </dynamicallyIncludedDestinations>
                      <staticallyIncludedDestinations>
                      </staticallyIncludedDestinations>
      </networkConnector>

      Though the duplex option is configured messages will not flow as follows:

      producer -> 5.3.0.4 -> 5.5.1-fuse-03-06 -> consumer

      However sending messages in the other direction does work:

      consumer <- 5.3.0.4 <- 5.5.1-fuse-03-06 <- producer

      It seems in the first case the duplex option is ignored. If the same network connector is used with brokers of the same version, messages can flow in both directions.

      Additionally if the network connector is defined in the 5.3.0.4 broker I see messages can flow in both directions.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                garytully Gary Tully
                Reporter:
                jsherman Jason Sherman
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: