activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <>
Subject Re: Problem upgrading from 5.5.1 to 5.6.0
Date Mon, 30 Jul 2012 10:19:37 GMT
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 from the same broker were
treated as the same thing in error.

On 27 July 2012 21:47, Guerrero <> wrote:
> After hitting a problem with a network of brokers (see this
> thread<>),
> I discovered the 5.6.0 release of ActiveMQ.  With the new release, I cannot
> seem to connect more than a single client to a server application.  I keep
> getting the InvalidClientIDException (with clientId ==
> "NC_localhost_outbound") in RegionBroker.addConnection(ConnectionContext,
> ConnectionInfo).  Extremely confused, I backed out to 5.5.1 and stepped
> through in debug, only to see that the previous context is removed rather
> than throwing an exception.
> I think I found the revision in branches/activemq-5.5 where the logic to
> remove a previous context was added:
> I cannot, however, find anything like that in the 5.6 branch or on trunk.
>  I don't know if I'm going down the wrong rabbit hole or what. Is there
> anything special that needs to be configured in 5.6 in order connect more
> than one remote broker?
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at


View raw message