activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fintan Bolton <fintan.bol...@iona.com>
Subject Re: zeroconf protocol unrecognized in ActiveMQ 5 broker
Date Mon, 08 Oct 2007 14:53:54 GMT

Thanks for the tip!  I didn't even know that there was a rendezvous connector
available---I'll give it a try.

But I do want to get zeroconf to work, as well.

Cheers,
Fintan


ttmdev wrote:
> 
> Try using the rendezvous connector (e.g.,  "rendezvous://cheese" ).
> 
> If that fails, you can always fall back on the multicast connector to
> auto-discover the brokers. 
> 
> Joe
> 
> 
> Fintan Bolton wrote:
>> 
>> If I try to add a zeroconf connector to the ActiveMQ message broker, for
>> example:
>> 
>>     <transportConnectors>
>>        <transportConnector name="zeroconf" uri="tcp://localhost:61717"
>> discoveryUri="zeroconf://_fuse."/>
>>     </transportConnectors>
>> 
>> I get the following error when I start the broker:
>> 
>> ERROR BrokerService                  - Failed to start ActiveMQ JMS
>> Message Broker. Reason: java.io.IOException: DiscoveryAgent scheme NOT
>> recognized: [zeroconf]
>> java.io.IOException: DiscoveryAgent scheme NOT recognized: [zeroconf]
>> 
>> It sounds like it most be a fairly elementary problem (e.g. missing JAR
>> file?).  I'm running the version of ActiveMQ that is embedded in FUSE
>> Message Broker 5.0.0.2.  Does anyone have an idea what's missing here?
>> 
>> Cheers,
>> Fintan
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/zeroconf-protocol-unrecognized-in-ActiveMQ-5-broker-tf4588169s2354.html#a13098266
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message