A bean of type Connection, from the master is what I was looking for.
There should be a clientId attribute, I want to understand how that is
unique.
To specify unique values in conf per installation, system
properties/env vars are the way to go and reference them in the xml
config using ${..}
the combination of networkConnector *name* attribute and brokerName of
a network needs to be unique.
Use a different name for each configured networkConnector element on a
given broker.
In 5.5.1, a reconnect (where the existing network connector is still
visible) and a second networkConnector
Hi Gary,
On Mon, Jul 30, 2012 at 12:19 PM, Gary Tully gary.tu...@gmail.com wrote:
the combination of networkConnector *name* attribute and brokerName of
a network needs to be unique.
Can in a network of brokers the individual brokers have the same names
(as long as they have different IP
Hi Martin,
that will be problematic because it will lead to a clash of clientids
used by the network connectors.
In your current setup on 5.5.0, can you inspect (on central) the
client id of some of the connected satellite networkConnectors and
post them. I want to understand how they are
gtully wrote
the combination of networkConnector *name* attribute and brokerName of
a network needs to be unique.
Use a different name for each configured networkConnector element on a
given broker.
Calling setName or setBrokerName with a unique string on the
NetworkConnector appears
Hi Gary,
On Mon, Jul 30, 2012 at 4:26 PM, Gary Tully gary.tu...@gmail.com wrote:
Hi Martin,
that will be problematic because it will lead to a clash of clientids
used by the network connectors.
In your current setup on 5.5.0, can you inspect (on central) the
client id of some of the
