activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] Commented: (AMQ-2344) Multicast works, but cannot be controlled
Date Wed, 05 Aug 2009 09:28:35 GMT


Gary Tully commented on AMQ-2344:

To configure how a client connects, add the parameters to the brokerURI on the client network
connector or connection factory. I think the fix for
may be necessary though to allow the parameters to be applied.

The discoveryUri has a limited number of parameters on the broadcast side but these should
be respected. things like the keepAlive and timeToLive, full details in

> 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