Re: Understanding MulticastDiscoveryAgentNotifier behavior.

2009-06-05 Thread Eric Bouer
RL: >> tcp://192.168.64.1:61616 >> 12:02:13,220  INFO FailoverTransport:714 - Successfully connected to >> tcp://192.168.0.1:61616 >> 12:02:13,222  INFO FailoverTransport:714 - Successfully connected to >> discovery:(multicast://224.1.2.3:6255?group=default) >> 12:02:18,731

Re: Understanding MulticastDiscoveryAgentNotifier behavior.

2009-06-05 Thread Claus Ibsen
ast://224.1.2.3:6255?group=default) > 12:02:18,731  INFO DiscoveryTransport:73 - Adding new broker connection URL: > tcp://192.168.0.1:61616 > 12:02:18,961  INFO FailoverTransport:714 - Successfully connected to > tcp://192.168.0.1:61616 > 12:02:18,963  INFO FailoverTransport:714 - S

Re: Understanding MulticastDiscoveryAgentNotifier behavior.

2009-06-05 Thread Willem Jiang
Hi, Does the thread exit when you just set the ActiveMQConnectionFactory with this URI tcp://localhost:61616. If so, I doubt it could be ActiveMQ issue. Willem Eric Bouer wrote: > Hello list. > I'm trying the following code to test multicast capabilities of > camel+activeMQ. > I found out that

Understanding MulticastDiscoveryAgentNotifier behavior.

2009-06-05 Thread Eric Bouer
FO FailoverTransport:714 - Successfully connected to tcp://192.168.0.1:61616 12:02:18,963 INFO FailoverTransport:714 - Successfully connected to discovery:(multicast://224.1.2.3:6255?group=default) . . . . http://www.nabble.com/file/p23885103/multicastdiscoveryagentnotifier.png -- View this me