There are some problems in its address parsing code that I am working on right now. I have not been able to confirm anthing beyond that yet.
- Jim -----Original Message----- From: Eric Bouer <ericbo...@gmail.com> Date: Mon, 1 Jun 2009 09:33:47 To: <users@activemq.apache.org> Subject: Re: Discovery and NMS Can anyone confirm it's working ? Or any other information on discovery in NMS ? semog wrote: > > I have not used the discovery code additions. Are there any unit test > samples that use it that might give you an idea on the format? If there > aren't, we should probably add some. You may want to look around for a > Java > sample. No guarantees, but it might give an indication on what the format > might be. > > On Tue, Mar 31, 2009 at 1:59 PM, JohnWest <john.w...@starz.com> wrote: > >> >> 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. >> >> > > -- View this message in context: http://www.nabble.com/Discovery-and-NMS-tp22812691p23817901.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
