activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gcollins <gareth.o.coll...@gmail.com>
Subject ActiveMQ Multicast Network Connection Loop?
Date Tue, 19 Mar 2013 04:21:08 GMT
Hi,

I have recently upgraded to 5.8.0 and I am noticing something weird when I
use the multicast protocol for the network connector. Here is the relevant
config (note that I am running in OSGi):

<networkConnectors>
            <networkConnector uri="multicast://default"/>
</networkConnectors>

<transportConnector name="openwire"
uri="nio://0.0.0.0:61616?maximumConnections=1000"
discoveryUri="multicast://default"/>

When I set up my broker with this config, I am seeing the broker connect to
itself:

[gsb@JCNJRD01 log]$ netstat -an | grep 61616
tcp        0      0 :::61616                    :::*                       
LISTEN      
tcp        0      0 ::ffff:127.0.0.1:61616      ::ffff:127.0.0.1:60954     
ESTABLISHED 
tcp        0      0 ::ffff:192.168.205.50:61616 ::ffff:192.168.205.50:52933
ESTABLISHED << HERE
tcp        0      0 ::ffff:192.168.205.50:52933 ::ffff:192.168.205.50:61616
ESTABLISHED << HERE
tcp        0      0 ::ffff:127.0.0.1:61616      ::ffff:127.0.0.1:60955     
ESTABLISHED 
tcp        0      0 ::ffff:127.0.0.1:60955      ::ffff:127.0.0.1:61616     
ESTABLISHED 
tcp        0      0 ::ffff:127.0.0.1:60954      ::ffff:127.0.0.1:61616     
ESTABLISHED

And when I put some real traffic through I am seeing lots of these errors:

"Duplicate message add attempt rejected"

Am I missing something obvious? If I comment out the network connector, the
loop goes away along with the "Duplicate message" errors.

When I ran with 5.7, I used similar configuration from a blueprint file (the
only difference was that I used TCP instead of nio) and I didn't have this
problem:

<networkConnectors>
          <networkConnector uri="multicast://default"/>
</networkConnectors>

<transportConnector name="openwire" uri="tcp://0.0.0.0:61616"
discoveryUri="multicast://default"/>

If anyone could tell me what foolish configuration error I have made (or
otherwise point me to "the error of my ways") it would be much appreciated.

thanks in advance,
Gareth Collins



--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-Multicast-Network-Connection-Loop-tp4664857.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message