I'm seeing a weird problem when using static network connectors in the latest
5.0 snapshots. If i specify the following in my activemq.xml. The following
happens when my local broker is running activemq 5.0 and the upstream
servers are using 4.1.1 or 5.0-SNAPSHOT. I also see the issue when using
4.1.1 instances but the error message is less verbose than the one listed
below.
<networkConncetors>
<networkConncetor name="nc1" uri="static:(tcp://server1:61616)"/>
<networkConncetor name="nc2" uri="static:(tcp://server2:61616)"/>
</networkConncetors>
or
<networkConncetors>
<networkConncetor name="nc1"
uri="static:(tcp://server1:61616,tcp://server2:61616)"/>
</networkConncetors>
I will see a pretty verbose stack trace with the following errors
(5.0-SNAPSHOT):
WARN TransportConnection - Failed to add Connection
javax.jms.InvalidClientIDException: Broker: localhost- Client:
NC_localhost_inboundlocalhost already connected from vm://localhost#0
a little bit further down I see the following
Async error occurred: javax.jms.InvalidClientIDException: Broker: localhost-
Client: NC_localhost_inboundlocalhost already connected from
vm://localhost#0
It continues to show this for a few times and then stops. I haven't tested
to see if the connections between the upstream brokers is connected, so I'm
not sure if this is affecting any use cases. I will try to post back with
more information regarding this.
The 4.1.1 instance shows the following...it seems to be the same sort of
error.
INFO DemandForwardingBridge - Network connection between vm://localhost#2
and tcp://server2:61616 shutdown due to local error:
javax.jms.InvalidClientIDException: Broker: localhost- Client:
NC_localhost_inboundlocalhost already connected
--
View this message in context:
http://www.nabble.com/InvalidClientIDException-when-using-valid-NetworkConnectors-in-activemq.xml-tf4714929s2354.html#a13477767
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
