activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dexter (JIRA)" <>
Subject [jira] Commented: (AMQ-2344) Multicast works, but cannot be controlled
Date Tue, 11 Aug 2009 08:54:35 GMT


Jason Dexter commented on AMQ-2344:

I found my problem and tested the solution keppAliveInterval=<n> after reading the MulticastDiscoveryAgent
With the following configuration the multicast packages are reduced massively (keepAliveInterval
default is DEFAULT_IDLE_TIME = 500)..

<transportConnector name="openwire" uri="tcp://" discoveryUri="multicast://default?keepAliveInterval=5000"/>

(The default value can be a problem with some smart switches not supporting IGMP snooping).

IMHO this issue can be closed.

> Multicast works, but cannot be controlled
> -----------------------------------------
>                 Key: AMQ-2344
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.2.0
>            Reporter: Jason Dexter
> I'm currently testing the network of brokers configuration (ref:
> Actually this works, but concerning the available parameters for discoveryUris, I do
not see any effect, when using a xbean configuration like
> <transportConnector name="openwire" uri="tcp://localhost:61616" discoveryUri="multicast://default?reconnectDelay=4000&amp;maxReconnectAttempts=10&amp;useExponentialBackOff=false&amp;initialReconnectDelay=5000"/>
> I do not want to produce much multicast traffic, because it is not necessary in my target
networks. Is there a way to let the above configured transport work as required?
> Or is this a local brain problem? ;-)
> Kind Regards

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message