Hi jim. First I'd like to thank you for your work. I guess you know that you can turn on auto-discovery and still make your broker not join the store-and-forward network. I just changed the multicast group name and brokers dont talk with each other. basically what I'm trying to do is to start my NMS client with this URI failover:(discovery:(multicast://default),tcp://somehost:61616) This URI works great with the java client.The NMS client fails. I ran my sniffer to see what packets are being sent from the client but I couldn't find anything interesting (UDP to multicast address) If I try only multicast://default it says that multicast transport is not supported. I'll be glad to provide more information to help you with this. Thanks again. Eric.
semog wrote: > > Hi Eric, > I have been trying to test whether discovery works, but I am not sure I > have > things configured correctly. I usually turn off the auto-discovery on the > broker because we have so many in our development environment that they > start to cross-talk with each other and contaminate our tests. I'm more > than happy to try some different scenarios out and add in some unit tests > if > there is a particular scenario you want to try out. > > Anybody else configured a broker and a client (Java) for auto-discovery? > > - Jim > > On Mon, Jun 1, 2009 at 9:33 AM, Eric Bouer <ericbo...@gmail.com> wrote: > >> >> 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. >> >> > > -- View this message in context: http://www.nabble.com/Discovery-and-NMS-tp22812691p23846582.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
