You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Eric Bouer <er...@gmail.com> on 2009/06/01 18:33:47 UTC
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 <Jo...@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.
Re: Discovery and NMS
Posted by Jim Gomes <e....@gmail.com>.
Eric,
Thanks for trying that out. At this point there isn't much more to try out since Tim has also confirmed that discovery is not working. We will push this out to the next version of NMS because we want to get 1.1 shipped. I don't think the next version will take as long as this one and discovery is the first major feature scheduled to be worked on. However if we are able to find a simple fix that can be thrown in during the release phase, I'm sure it can be considered.
- Jim
-----Original Message-----
From: Eric Bouer <er...@gmail.com>
Date: Wed, 10 Jun 2009 14:21:37
To: <us...@activemq.apache.org>
Subject: Re: Discovery and NMS
Hello Jim
Unfortunately I can't confirm it's working
Using activemq:failover
(discovery:multicast://default,tcp://activemqhost:61616)
I've got :
"Connect fail to 'discovery:multicast://default': Composite connection not
supported with MulticastDiscovery transport."
Using activemq:discovery:multicast://default I've got:
Connect failed :Apache.NMS.NMSConnectionException: Unable to find a
connection
to discovery:multicast://default before the timeout period expired.
at
Apache.NMS.ActiveMQ.Transport.Discovery.DiscoveryTransportFactory.CreateTransport(Uri
location)
at Apache.NMS.ActiveMQ.Transport.TransportFactory.CreateTransport(Uri
location)
at Apache.NMS.ActiveMQ.ConnectionFactory.CreateConnection(String
userName,
String password)
at Apache.NMS.ActiveMQ.ConnectionFactory.CreateConnection()
at ActiveMQConnector.MQ.Connect()
Tried again trunk from today.
Can I help you with more information or anything else?
Thanks.
Eric.
semog wrote:
>
> Hi Eric (And John West),
>
> I haven't been able to get the auto-discovery to work yet, but from your
> sample connection strings, I think you will need to change them to the
> following to have any chance of getting them to work:
>
> activemq:discovery:multicast://default
>
> or
>
> activemq:failover:discovery:multicast://default
>
> Parenthesis are also acceptable as follows:
>
> activemq:discovery:(multicast://default)
> activemq:failover:(discovery:multicast://default,tcp://activemqhost:61616)
>
> The key is to have the prefix of "activemq:". If you don't have that,
> then the correct connection factory will not be loaded by NMS. Make sure
> you update to the latest code and rebuild the Apache.NMS and
> Apache.NMS.ActiveMQ projects before trying anything. The discovery
> protocol stuff is not my area of expertise, so I'm still attempting to
> figure out the mechanisms behind it.
>
> Best,
> Jim
>
--
View this message in context: http://www.nabble.com/Discovery-and-NMS-tp22812691p23971301.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Discovery and NMS
Posted by Eric Bouer <er...@gmail.com>.
Thanks Tim.
It's much better now. And it seems to work.
I'll be doing some tests with it for the next week.
There is however, a very annoying bug with the parallel Java functionality:
https://issues.apache.org/activemq/browse/AMQ-2283
So it's too soon to be happy ... :)
Thanks again.
Timothy Bish wrote:
>
> On Wed, 2009-06-10 at 14:21 -0700, Eric Bouer wrote:
>> Hello Jim
>> Unfortunately I can't confirm it's working
>> Using activemq:failover
>> (discovery:multicast://default,tcp://activemqhost:61616)
>> I've got :
>> "Connect fail to 'discovery:multicast://default': Composite connection
>> not
>> supported with MulticastDiscovery transport."
>
> I'm seeing this error to, seems there might be a bug here.
>>
>> Using activemq:discovery:multicast://default I've got:
>>
>> Connect failed :Apache.NMS.NMSConnectionException: Unable to find a
>> connection
>> to discovery:multicast://default before the timeout period expired.
>> at
>> Apache.NMS.ActiveMQ.Transport.Discovery.DiscoveryTransportFactory.CreateTransport(Uri
>> location)
>> at Apache.NMS.ActiveMQ.Transport.TransportFactory.CreateTransport(Uri
>> location)
>> at Apache.NMS.ActiveMQ.ConnectionFactory.CreateConnection(String
>> userName,
>> String password)
>> at Apache.NMS.ActiveMQ.ConnectionFactory.CreateConnection()
>> at ActiveMQConnector.MQ.Connect()
>>
>> Tried again trunk from today.
>> Can I help you with more information or anything else?
>> Thanks.
>> Eric.
>>
>
> I submitted a patch this morning that should get the Discovery Transport
> working for you if you checkout the latest trunk code. If you want to
> give that a try and let us know if things start to work for you that
> would be great.
>
>
>>
>>
>> semog wrote:
>> >
>> > Hi Eric (And John West),
>> >
>> > I haven't been able to get the auto-discovery to work yet, but from
>> your
>> > sample connection strings, I think you will need to change them to the
>> > following to have any chance of getting them to work:
>> >
>> > activemq:discovery:multicast://default
>> >
>> > or
>> >
>> > activemq:failover:discovery:multicast://default
>> >
>> > Parenthesis are also acceptable as follows:
>> >
>> > activemq:discovery:(multicast://default)
>> >
>> activemq:failover:(discovery:multicast://default,tcp://activemqhost:61616)
>> >
>> > The key is to have the prefix of "activemq:". If you don't have that,
>> > then the correct connection factory will not be loaded by NMS. Make
>> sure
>> > you update to the latest code and rebuild the Apache.NMS and
>> > Apache.NMS.ActiveMQ projects before trying anything. The discovery
>> > protocol stuff is not my area of expertise, so I'm still attempting to
>> > figure out the mechanisms behind it.
>> >
>> > Best,
>> > Jim
>> >
>>
> --
> Tim Bish
> http://fusesource.com
> http://timbish.blogspot.com/
>
>
>
>
>
--
View this message in context: http://www.nabble.com/Discovery-and-NMS-tp22812691p23995583.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Discovery and NMS
Posted by Timothy Bish <ta...@gmail.com>.
On Wed, 2009-06-10 at 14:21 -0700, Eric Bouer wrote:
> Hello Jim
> Unfortunately I can't confirm it's working
> Using activemq:failover
> (discovery:multicast://default,tcp://activemqhost:61616)
> I've got :
> "Connect fail to 'discovery:multicast://default': Composite connection not
> supported with MulticastDiscovery transport."
I'm seeing this error to, seems there might be a bug here.
>
> Using activemq:discovery:multicast://default I've got:
>
> Connect failed :Apache.NMS.NMSConnectionException: Unable to find a
> connection
> to discovery:multicast://default before the timeout period expired.
> at
> Apache.NMS.ActiveMQ.Transport.Discovery.DiscoveryTransportFactory.CreateTransport(Uri
> location)
> at Apache.NMS.ActiveMQ.Transport.TransportFactory.CreateTransport(Uri
> location)
> at Apache.NMS.ActiveMQ.ConnectionFactory.CreateConnection(String
> userName,
> String password)
> at Apache.NMS.ActiveMQ.ConnectionFactory.CreateConnection()
> at ActiveMQConnector.MQ.Connect()
>
> Tried again trunk from today.
> Can I help you with more information or anything else?
> Thanks.
> Eric.
>
I submitted a patch this morning that should get the Discovery Transport
working for you if you checkout the latest trunk code. If you want to
give that a try and let us know if things start to work for you that
would be great.
>
>
> semog wrote:
> >
> > Hi Eric (And John West),
> >
> > I haven't been able to get the auto-discovery to work yet, but from your
> > sample connection strings, I think you will need to change them to the
> > following to have any chance of getting them to work:
> >
> > activemq:discovery:multicast://default
> >
> > or
> >
> > activemq:failover:discovery:multicast://default
> >
> > Parenthesis are also acceptable as follows:
> >
> > activemq:discovery:(multicast://default)
> > activemq:failover:(discovery:multicast://default,tcp://activemqhost:61616)
> >
> > The key is to have the prefix of "activemq:". If you don't have that,
> > then the correct connection factory will not be loaded by NMS. Make sure
> > you update to the latest code and rebuild the Apache.NMS and
> > Apache.NMS.ActiveMQ projects before trying anything. The discovery
> > protocol stuff is not my area of expertise, so I'm still attempting to
> > figure out the mechanisms behind it.
> >
> > Best,
> > Jim
> >
>
--
Tim Bish
http://fusesource.com
http://timbish.blogspot.com/
Re: Discovery and NMS
Posted by Eric Bouer <er...@gmail.com>.
Hello Jim
Unfortunately I can't confirm it's working
Using activemq:failover
(discovery:multicast://default,tcp://activemqhost:61616)
I've got :
"Connect fail to 'discovery:multicast://default': Composite connection not
supported with MulticastDiscovery transport."
Using activemq:discovery:multicast://default I've got:
Connect failed :Apache.NMS.NMSConnectionException: Unable to find a
connection
to discovery:multicast://default before the timeout period expired.
at
Apache.NMS.ActiveMQ.Transport.Discovery.DiscoveryTransportFactory.CreateTransport(Uri
location)
at Apache.NMS.ActiveMQ.Transport.TransportFactory.CreateTransport(Uri
location)
at Apache.NMS.ActiveMQ.ConnectionFactory.CreateConnection(String
userName,
String password)
at Apache.NMS.ActiveMQ.ConnectionFactory.CreateConnection()
at ActiveMQConnector.MQ.Connect()
Tried again trunk from today.
Can I help you with more information or anything else?
Thanks.
Eric.
semog wrote:
>
> Hi Eric (And John West),
>
> I haven't been able to get the auto-discovery to work yet, but from your
> sample connection strings, I think you will need to change them to the
> following to have any chance of getting them to work:
>
> activemq:discovery:multicast://default
>
> or
>
> activemq:failover:discovery:multicast://default
>
> Parenthesis are also acceptable as follows:
>
> activemq:discovery:(multicast://default)
> activemq:failover:(discovery:multicast://default,tcp://activemqhost:61616)
>
> The key is to have the prefix of "activemq:". If you don't have that,
> then the correct connection factory will not be loaded by NMS. Make sure
> you update to the latest code and rebuild the Apache.NMS and
> Apache.NMS.ActiveMQ projects before trying anything. The discovery
> protocol stuff is not my area of expertise, so I'm still attempting to
> figure out the mechanisms behind it.
>
> Best,
> Jim
>
--
View this message in context: http://www.nabble.com/Discovery-and-NMS-tp22812691p23971301.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Discovery and NMS
Posted by semog <e....@gmail.com>.
Hi Eric (And John West),
I haven't been able to get the auto-discovery to work yet, but from your
sample connection strings, I think you will need to change them to the
following to have any chance of getting them to work:
activemq:discovery:multicast://default
or
activemq:failover:discovery:multicast://default
Parenthesis are also acceptable as follows:
activemq:discovery:(multicast://default)
activemq:failover:(discovery:multicast://default,tcp://activemqhost:61616)
The key is to have the prefix of "activemq:". If you don't have that, then
the correct connection factory will not be loaded by NMS. Make sure you
update to the latest code and rebuild the Apache.NMS and Apache.NMS.ActiveMQ
projects before trying anything. The discovery protocol stuff is not my
area of expertise, so I'm still attempting to figure out the mechanisms
behind it.
Best,
Jim
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.
--
View this message in context: http://www.nabble.com/Discovery-and-NMS-tp22812691p23954678.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Discovery and NMS
Posted by Eric Bouer <er...@gmail.com>.
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 <er...@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 <Jo...@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.
Re: Discovery and NMS
Posted by Jim Gomes <e....@gmail.com>.
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 <er...@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 <Jo...@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.
>
>
Re: Discovery and NMS
Posted by Jim Gomes <e....@gmail.com>.
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 <er...@gmail.com>
Date: Mon, 1 Jun 2009 09:33:47
To: <us...@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 <Jo...@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.