Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <22812691.post@talk.nabble.com>
Date: Tue, 31 Mar 2009 13:59:55 -0700 (PDT)
From: JohnWest <John.West@starz.com>
To: users@activemq.apache.org
Subject: Discovery and NMS
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


I tried using Discovery to find my ActiveMQ broker from an NMS client. The
broker config includes:

        <transportConnectors>
            <transportConnector name="openwire" uri="tcp://localhost:61616"
discoveryUri="multicast://default"/>
            <transportConnector name="ssl" uri="ssl://localhost:61617"/>
            <transportConnector name="stomp" uri="stomp://localhost:61613"/>
            <transportConnector name="xmpp" uri="xmpp://localhost:61222"/>
        </transportConnectors>

In the pub/sub sample publisher, I setup the following:

        const string BROKER =
"discovery:(multicast://default)?initialReconnectDelay=100";

This got me an error parsing IP address error out of the Discovery Agent.
What am I doing wrong?
-- 
View this message in context: http://www.nabble.com/Discovery-and-NMS-tp22812691p22812691.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.