Note, I can't get rendezvous to work either.
<transportConnector name="openwire" uri="tcp://localhost:61616"
discoveryUri="rendezvous://test"/>
String brokerUrl =
"discovery:(rendezvous://test)?maxReconnectAttempts=2";
ActiveMQConnectionFactory connectionFactory =
new ActiveMQConnectionFactory(brokerUrl);
However in this case I can at least see (using jmDNS) that there is in fact
an entry for _test.ActiveMQ-4. which contains the correct broker URL.
I can also put a breakpoint at FailoverTransport.add(URI u[]) and see that
the correct URI is being added, namely "tcp://hostname:61616" which, if I
configure directly into the ActiveMQConnectionFactory works.
So this is looking like a bug to me.
BigPic wrote:
>
> I'm using ActiveMQ 5.2.0 but I can't get clients to discover the broker.
> My goal is to run a single broker with multiple clients all
> auto-discovering it.
>
> I have the broker config:
>
> <transportConnectors>
> <transportConnector name="openwire"
> uri="tcp://localhost:61616"
> discoveryUri="multicast://default?group=test"/>
> </transportConnectors>
>
> and the broker is running on a Win2K system.
>
> Then on another system (Win XP SP3), I have a Java 1.5 client:
>
> String brokerUrl =
> "discovery:(multicast://default)?group=test&maxReconnectAttempts=2";
> ActiveMQConnectionFactory connectionFactory =
> new ActiveMQConnectionFactory(brokerUrl);
>
>
> But the client just gives me:
>
> ERROR: org.apache.activemq.transport.failover.FailoverTransport - Failed
> to connect to transport after: 2 attempt(s)
> Caught: javax.jms.JMSException: No uris available to connect to.
>
>
>
--
View this message in context:
http://www.nabble.com/Multicast-Discovery-not-working-tp21344587p21346016.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
