From users-return-10902-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org Mon Oct 08 14:54:26 2007 Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 19225 invoked from network); 8 Oct 2007 14:54:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Oct 2007 14:54:26 -0000 Received: (qmail 91959 invoked by uid 500); 8 Oct 2007 14:54:13 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 91641 invoked by uid 500); 8 Oct 2007 14:54:13 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 91632 invoked by uid 99); 8 Oct 2007 14:54:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Oct 2007 07:54:13 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Oct 2007 14:54:14 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1IetzW-0001TS-1k for users@activemq.apache.org; Mon, 08 Oct 2007 07:53:54 -0700 Message-ID: <13098266.post@talk.nabble.com> Date: Mon, 8 Oct 2007 07:53:54 -0700 (PDT) From: Fintan Bolton To: users@activemq.apache.org Subject: Re: zeroconf protocol unrecognized in ActiveMQ 5 broker In-Reply-To: <13096937.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: fintan.bolton@iona.com References: <13096575.post@talk.nabble.com> <13096937.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org 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: >> >> >> > discoveryUri="zeroconf://_fuse."/> >> >> >> 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.