[ 
https://issues.apache.org/activemq/browse/AMQ-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53468#action_53468
 ] 

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 
https://issues.apache.org/activemq/browse/AMQ-2283 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 
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/transport/discovery/multicast/MulticastDiscoveryAgent.java

> Multicast works, but cannot be controlled
> -----------------------------------------
>
>                 Key: AMQ-2344
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2344
>             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: 
> http://activemq.apache.org/networks-of-brokers.html)
> 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.

Reply via email to