Re: Multicast Discovery with non-default group name not working

for setting group field and AbstractDiscoveryAgent does, the group parameter value in the uri will be set to the group field in AbstractDiscoveryAgent instead of the one in MulticastDiscoveryAgent. -- View this message in context: http://activemq.2283324.n4.nabble.com/Multicast-Discovery

Re: Multicast Discovery with non-default group name not working

Another question, does ActiveMQ support publisher broadcast messages to consumers directly using multicast? -- View this message in context: http://activemq.2283324.n4.nabble.com/Multicast-Discovery-with-non-default-group-name-not-working-tp4682758p4682805.html Sent from the ActiveMQ - User

Multicast Discovery with non-default group name not working

this message in context: http://activemq.2283324.n4.nabble.com/Multicast-Discovery-with-non-default-group-name-not-working-tp4682758.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

multicast discovery - localhost in UDP packets

TransportConnector with a multicast discovery URI), I can get the message to include tcp://Michael-Dell:X, but that hostname isn't a real network location--just my local computer name. Any advice? Here's the simplest version of my initial test with the peer: transport. private static final

Re: CountDownLatch problem . MultiCast Discovery and refusal of connection on DUPLEX connection (Fuse 5.3.0.5) .

DemandForwardingBridge         - SIBBusSupervisor-tpnocp11v-bus bridge to SIBBusModule-NOCP5-tpnocp08s-bus stopped Eric-AWL -- View this message in context: http://old.nabble.com/MultiCast-Discovery-and-refusal-of-connection-tp28827529p29084235.html Sent from the ActiveMQ - User mailing

Re: CountDownLatch problem . MultiCast Discovery and refusal of connection on DUPLEX connection (Fuse 5.3.0.5) .

Eric-AWL -- View this message in context: http://old.nabble.com/MultiCast-Discovery-and-refusal-of-connection-tp28827529p29084235.html Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://blog.garytully.com Open Source Integration http://fusesource.com

CountDownLatch problem . MultiCast Discovery and refusal of connection on DUPLEX connection (Fuse 5.3.0.5) .

stopped Eric-AWL -- View this message in context: http://old.nabble.com/MultiCast-Discovery-and-refusal-of-connection-tp28827529p29083434.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

CountDownLatch problem . MultiCast Discovery and refusal of connection on DUPLEX connection (Fuse 5.3.0.5) .

] INFO DemandForwardingBridge - SIBBusSupervisor-tpnocp11v-bus bridge to SIBBusModule-NOCP5-tpnocp08s-bus stopped Eric-AWL -- View this message in context: http://old.nabble.com/MultiCast-Discovery-and-refusal-of-connection-tp28827529p29084235.html Sent from the ActiveMQ - User

Re: CountDownLatch problem . MultiCast Discovery and refusal of connection on DUPLEX connection (Fuse 5.3.0.5) .

:2010-06-22 22:58:44,328 [26.190.27:40519] INFO DemandForwardingBridge         - SIBBusSupervisor-tpnocp11v-bus bridge to SIBBusModule-NOCP5-tpnocp08s-bus stopped Eric-AWL -- View this message in context: http://old.nabble.com/MultiCast-Discovery-and-refusal-of-connection

Re: CountDownLatch problem . MultiCast Discovery and refusal of connection on DUPLEX connection (Fuse 5.3.0.5) .

established. activemq-server.log:2010-06-22 22:58:44,328 [26.190.27:40519] INFO DemandForwardingBridge         - SIBBusSupervisor-tpnocp11v-bus bridge to SIBBusModule-NOCP5-tpnocp08s-bus stopped Eric-AWL -- View this message in context: http://old.nabble.com/MultiCast-Discovery-and-refusal

Re: MultiCast Discovery and refusal of connection

://old.nabble.com/MultiCast-Discovery-and-refusal-of-connection-tp28827529p28839417.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

MultiCast Discovery and refusal of connection

Hi everybody Is there a reason that can explain that a Multicast Discovery network connector refuses to connect to a distant broker (even after the reconnect delay) ? I verified with sniffer that (in principle) correct multicast frame was present on the subnetwork. Thank you in advance

Re: MultiCast Discovery and refusal of connection

://www.ttmsolutions.com Eric-AWL wrote: Hi everybody Is there a reason that can explain that a Multicast Discovery network connector refuses to connect to a distant broker (even after the reconnect delay) ? I verified with sniffer that (in principle) correct multicast frame was present

broker name always localhost in multicast discovery event

Since version 5.0, the broker name in multicast discovery event is always localhost. Is it a bug? Alan -- View this message in context: http://old.nabble.com/broker-name-always-%22localhost%22-in-multicast-discovery-event-tp28807464p28807464.html Sent from the ActiveMQ - User mailing list

Multicast discovery doesn't seem to work currently.

Hi I'm currently in a situation where I have a (multicast discovery) network of brokers of some brokers (15). One component A has a network connector (duplex) to the 14 others which have an associated transport connector. The 14 others components discovered and connected themselves on the same

Re: Multicast Discovery and network connections

that error seems more like multicast is not supported rather than there is no network. If you disable multicast discovery/publish, can the regular tcp transport connector start and listen? Unfortunately there is no retry on the inital start procedure of activemq. If a configured services

Re: Multicast Discovery and network connections

can you expand on what you are seeing? 2009/10/23 Ryan Moquin fragility...@gmail.com I've had problems with the multicast discovery in activemq when a network connection isn't present, as well as others. Is that really an expected behavior? Is there any reason that activemq couldn't

Multicast Discovery and network connections

I've had problems with the multicast discovery in activemq when a network connection isn't present, as well as others. Is that really an expected behavior? Is there any reason that activemq couldn't gracefully handle that situation by just logging a message until the network connection

Re: Build up of Threads using Multicast Discovery Agent - eventually out of memory

Hi Gary, The issue already contains a test case to re-produce. Like the reporter I am also using multicast discover in it's simplest form and the problem occurs so I would guess this is a general problem for multicast discovery. BRegards Andrew Gary Tully wrote: this seems

broker dead block. Multicast Discovery Notifier thread doesn't stop

-2 : internal broker is gracefully stopped In this situation, on A, the instance-nc multicast Discovery thread and scheduler, doesn't want to stop. (see thread dump) With trace on, I see that conn2 (A-B:61602) is closed when B is killed. I see that instance-nc networkConnector is closed when A's

Re: Build up of Threads using Multicast Discovery Agent - eventually out of memory

runs out of memory after a few days. I ran jconsole against it and notice that the threads are building up and up. In the Threads section of jconsole, I see that the vast majority of Threads are Multicast Discovery Agent Notifier so I think the problem is related to this. My application uses

Re: Build up of Threads using Multicast Discovery Agent - eventually out of memory

section of jconsole, I see that the vast majority of Threads are Multicast Discovery Agent Notifier so I think the problem is related to this. My application uses ActiveMQ message broker and Camel router internally and sends messages to other external message brokers which it discovers using

Build up of Threads using Multicast Discovery Agent - eventually out of memory

Hi, I have a problem that my application runs out of memory after a few days. I ran jconsole against it and notice that the threads are building up and up. In the Threads section of jconsole, I see that the vast majority of Threads are Multicast Discovery Agent Notifier so I think the problem

New Persistent Multicast discovery agent for each message.

Hello list. I'm trying the following code to test multicast capabilities of camel+activeMQ. I found out that a new thread is started for each message I send, but that thread is staying alive for the whole program lifetime. The number of live multicast discovery agent notifier threads scales up

multicast discovery and ?group=parameter

http://activemq.apache.org/discovery-transport-reference.html can someone explain or point to the explanation in the docs about the group parameter in multicast discovery? What is the difference between specifying different group and specifying a different multicast address? The reason why

Re: multicast discovery and ?group=parameter

to the explanation in the docs about the group parameter in multicast discovery? What is the difference between specifying different group and specifying a different multicast address? The reason why I'm asking is that I've seen connection attempts to my broker from clients having multicast://default?group

Re: Multicast Discovery not working

a connection I need to have at least 10 reconnect attempts and set useExponentialBackOff=true. -- View this message in context: http://www.nabble.com/Multicast-Discovery-not-working-tp21344587p21571951.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Multicast Discovery not working

to have at least 10 reconnect attempts and set useExponentialBackOff=true. -- View this message in context: http://www.nabble.com/Multicast-Discovery-not-working-tp21344587p21484957.html Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://blog.garytully.com

Re: Multicast Discovery not working

second) delay between attempts. To get a connection I need to have at least 10 reconnect attempts and set useExponentialBackOff=true. -- View this message in context: http://www.nabble.com/Multicast-Discovery-not-working-tp21344587p21484957.html Sent from the ActiveMQ - User mailing list

Re: Multicast Discovery not working

this. I tried removing the group id but that didn't help. I'm at a loss for what to try next. Can anyone suggest a way for me to move forward with this? Thanks. -- View this message in context: http://www.nabble.com/Multicast-Discovery-not-working-tp21344587p21344587.html Sent from

Multicast Discovery not working

help me debug this. I tried removing the group id but that didn't help. I'm at a loss for what to try next. Can anyone suggest a way for me to move forward with this? Thanks. -- View this message in context: http://www.nabble.com/Multicast-Discovery-not-working-tp21344587p21344587.html Sent

Re: Multicast Discovery not working

: ERROR: org.apache.activemq.transport.failover.FailoverTransport - Failed to connect to transport after: 2 attempt(s) Caught: javax.jms.JMSException: No uris available to connect to. -- View this message in context: http://www.nabble.com/Multicast-Discovery-not-working

Re: Disable multicast discovery

://www.nabble.com/Disable-multicast-discovery-tp21132232p21143303.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Disable multicast discovery

in the background... -- View this message in context: http://www.nabble.com/Disable-multicast-discovery-tp21132232p21132304.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

RE: Disable multicast discovery

Why don't you just hard code the url of the broker and not use discovery all together? -Original Message- From: Ben Amitai [mailto:saba...@gmail.com] Sent: 2008-12-22 1:05 PM To: users@activemq.apache.org Subject: Disable multicast discovery Hello, My application has one and only

Multicast discovery

documentation to explain it.. Thank's Udi -- View this message in context: http://www.nabble.com/Multicast-discovery-tp20879162p20879162.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Restricting Multicast Discovery

On 27/03/2008, carbon60 [EMAIL PROTECTED] wrote: I apologize for asking basic questions! I am trying to configure multicast discovery among brokers on an insecure network. Is this possible or a good idea? I don't know much about multicast, so I don't understand how to restrict which

Re: Restricting Multicast Discovery

James.Strachan wrote: On 27/03/2008, carbon60 [EMAIL PROTECTED] wrote: I apologize for asking basic questions! I am trying to configure multicast discovery among brokers on an insecure network. Is this possible or a good idea? I don't know much about multicast, so I don't

Re: Restricting Multicast Discovery

On 28/03/2008, carbon60 [EMAIL PROTECTED] wrote: James.Strachan wrote: On 27/03/2008, carbon60 [EMAIL PROTECTED] wrote: I apologize for asking basic questions! I am trying to configure multicast discovery among brokers on an insecure network. Is this possible or a good

Restricting Multicast Discovery

I apologize for asking basic questions! I am trying to configure multicast discovery among brokers on an insecure network. Is this possible or a good idea? I don't know much about multicast, so I don't understand how to restrict which systems get connected. Thanks, A. -- View this message

Re: Network of brokers + multicast discovery, programmatically

That looks much more simple! I do have one problem remaining with that setup though : my messages seem to be discarded by the listener because of a TTL=1, and I didn't find anyplace to change it. My test config is a sender on a host and a listener on another host. The message I get on the

Network of brokers + multicast discovery, programmatically

I'm trying to set up multiple clients, each one with its own embedded broker to which it talks in-VM, and to have all the brokers connected in a network through multicast discovery. I need to do this programmatically (so no xml configuration). I'm testing this with just two nodes so far

Re: Multicast Discovery connection

The CPP client doesn't support discovery. Regards Tim On Fri, 2007-10-19 at 11:10 -0700, appi03 wrote: I am trying to use the multicast discovery protocol and having some trouble with it. I think i have the broker configuration down. Client 1 (Producer) - Broker 1 transportConnector uri

Re: Multicast Discovery connection

the multicast discovery protocol and having some trouble with it. I think i have the broker configuration down. Client 1 (Producer) - Broker 1 transportConnector uri=tcp://localhost:61616 discoveryUri=multicast://prod1/ networkConnector name=producer uri=multicast://prod1

Re: Multicast Discovery connection

any idea please let me know. thanks, arpit -- View this message in context: http://www.nabble.com/Multicast-Discovery-connection-tf4654948s2354.html#a13301251 Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Multicast Discovery connection

I am trying to use the multicast discovery protocol and having some trouble with it. I think i have the broker configuration down. Client 1 (Producer) - Broker 1 transportConnector uri=tcp://localhost:61616 discoveryUri=multicast://prod1/ networkConnector name=producer uri=multicast://prod1

Multicast Discovery hangs if there is no broker

Hi, I am using ActiveMQ 4.1.1 with Multicast Discovery for client to find the broker, thus we can avoid hard coding any physical hosts in the config. After discovery, the real communication still is through TCP. However, we found that the MulticastDiscoveryAgent will simply hang there forever