It is a requirement, because on reconnect due to a network partition
of two non unique network connectors, if the target broker has not
noticed the disconnect, it was possible to get duplicate network
connectors created and potential for deadlock. Having them explicitly
named allows reliable
Hey Gary,
This all sounds very reasonable to me, but to confirm the issue you referenced
was for connectors with duplex enabled, but our connectors do not have duplex
enabled (unless it's enabled by default). My guess is that network connector
names have to be unique, regardless of whether
Just a follow-up post to that network-of-brokers thread.
Let me know if you already subscribe to the Activemq users forum. If so, I
will stop sending you copies of things that may be interesting.
Cheers,
sv
sasasasasasasasasasasasasasasasasasasasasasasasasasasasasasasasas
Stephen Vincent
Hello again,
We are from AMQ 5.4.0 to 5.6.0, and there appears to be a new uniqueness
constraint in network connector names in network-of-brokers configurations.
Here's our setup:
- N copies of a producer application; each copy of the producer application
consists of an embedded broker with 2
