en Vincent
Platform R&D
Tel: + 1 919 531 7556
stephen.vinc...@sas.com
SAS ... THE POWER TO KNOW
-Original Message-
From: Geoffrey Arnold [mailto:geoffrey.arn...@gmail.com]
Sent: Monday, May 21, 2012 3:58 PM
To: users@activemq.apache.org
Subject: Re: Problem with network-of-brokers confi
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 du
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 duplic
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 n
