activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dexter (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-2344) Multicast works, but cannot be controlled
Date Tue, 11 Aug 2009 09:30:35 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jason Dexter resolved AMQ-2344.
-------------------------------

       Resolution: Working as Designed
    Fix Version/s: 5.2.0

as commented...

> 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
>             Fix For: 5.2.0
>
>
> 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.


Mime
View raw message