Affects Version/s: 5.5.1-fuse-03-06
Fix Version/s: 5.5.1-fuse-04-01
Environment:Fuse Message Broker 5.5.1-fuse-03-06
Fuse Message Broker 188.8.131.52
Similar Issues:Show 10 results
MB-813 Duplex http network connector not reliably reestablished in an unstable network MB-744 Hang when load testing duplex network connector MB-1263 Network Dead Lock using duplex network connector for NOB MB-464 excludedDestinations property for a duplex network connector causes messages to be dispatched from the target queue and discarded MB-385 Messages are lost if duplex is set to "true" MB-433 ActiveMQ duplex connector inboud connection does not inherit all policies from outboud connection MB-24 Network Connection leverage the non blocking sync sends implemented in MB-23 MB-982 Failover issues in network connector MB-837 Wildcards do not work with included destinations for network connectors. MB-253 Network Connector issue in ActiveMQ.xml
External Issue URL:
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
Though the duplex option is configured messages will not flow as follows:
producer -> 184.108.40.206 -> 5.5.1-fuse-03-06 -> consumer
However sending messages in the other direction does work:
consumer <- 220.127.116.11 <- 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 18.104.22.168 broker I see messages can flow in both directions.