scoveryAgent didn't define the property 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.228332
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
ntered same issue?
Thanks in advance.
Regards,
Milo
--
View 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.
rt manually (a tcp://0.0.0.0:0 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 pe
t;>
>>>>>> 2010-06-22 22:58:42,648 [-tpnocp08s-bus]] INFO
>>>>>> DiscoveryNetworkConnector
>>>>>> - Establishing network connection from
>>>>>> vm://SIBBusModule-NOCP5-tpnocp08s-bus to
>>>>>> tcp://tpnocp11v-bus.vd
t;>>> 2010-06-22 22:59:18,033 [NetworkBridge ] INFO DemandForwardingBridge
>>>>> - SIBBusModule-NOCP5-tpnocp08s-bus bridge to Unknown stopped
>>>>>
>>>>>
>>>>> Here is the other side corresponding activemq trace
>
gt;>>> SIBBusModule-NOCP5-tpnocp08s-bus
>>>>
>>>> activemq-server.log:2010-06-22 22:56:24,438 [26.190.27:40517] INFO
>>>> DemandForwardingBridge - SIBBusSupervisor-tpnocp11v-bus bridge
>>>> to
>>>> SIBBusModule-NOCP5-tpnocp08s-bus sto
- Created Duplex Bridge back to
>>> SIBBusModule-NOCP5-tpnocp08s-bus
>>> activemq-server.log:2010-06-22 22:56:26,135 [ocp11v-bus#1770] INFO
>>> DemandForwardingBridge - Network connection between
>>> vm://SIBBusSupervisor-tpnocp11v-bus#1770 and
>&g
t;>
>> activemq-server.log:2010-06-22 22:57:34,818 [26.190.27:40518] INFO
>> DemandForwardingBridge - SIBBusSupervisor-tpnocp11v-bus bridge to
>> SIBBusModule-NOCP5-tpnocp08s-bus stopped
>>
>> activemq-server.log:2010-06-22 22:57:39,153 [26.190.27:40519] INFO
>> Transpo
on between
> vm://SIBBusSupervisor-tpnocp11v-bus#1806 and
> tcp:///10.26.190.27:40519(SIBBusModule-NOCP5-tpnocp08s-bus) has been
> 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-of-connection-tp28827529p29084235.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
us bridge to
SIBBusModule-NOCP5-tpnocp08s-bus 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.
Hi
With 5.2.0, I have some explicit log traces which can help to find the
origin of the problem. I just opened the AMQ-2774 case.
The problem appears when
- the multicast discovery process discovered a distant broker.
a line "Establishing ..." appears in the log file
- But the
> has been biting lots of folks.
>
> https://issues.apache.org/activemq/browse/AMQ-2094
>
> Can you telnet to your 'distant' broker?
>
> Joe
> http://www.ttmsolutions.com
>
--
View this message in context:
http://old.nabble.com/MultiCast-Discovery-and-refusal-of-connection-tp28827529p28839417.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
7; broker?
Joe
http://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)
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 for
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 ma
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 th
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 are not
at
org.apache.activemq.xbean.XBeanBrokerService.afterPropertiesSet(XBean
BrokerService.java:56)
On Fri, Oct 23, 2009 at 6:47 AM, Gary Tully wrote:
> can you expand on what you are seeing?
>
> 2009/10/23 Ryan Moquin
>
> > I've had problems with the multicast discovery in activemq when a network
> > connection isn
can you expand on what you are seeing?
2009/10/23 Ryan Moquin
> 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
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 networ
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 see
conn1 is gracefully stopped and close
7-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 "
ice 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 applicat
ut 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
> relat
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&
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" th
e 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
>
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
ion attempts pass before the discovery agent discovers the
>> broker.
>>
>> #3 is definitely a bug. If I use
>>
>> String brokerUrl =
>> "discovery:(multicast://default?group=test)?maxReconnectAttempts=30&initialReconnectDelay=1000&useExponential
;initialReconnectDelay=1000&useExponentialBackOff=false";
>
> the connection still fails, and in far less than the 30 seconds that should
> be necessary to do 30 attempts with a 1000 ms (= 1 second) delay between
> attempts. To get a connection I need to have at least 10 recon
till fails, and in far less than the 30 seconds that should
be necessary to do 30 attempts with a 1000 ms (= 1 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 archive at Nabble.com.
ce and a few other pages but I haven't found
> anything that would 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?
>
>
ent just gives me:
>
> 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-tp21344587p21346016.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
#x27;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 the ActiveMQ - User mailing list archive at Nabble.com.
Joe
> Free ActiveMQ user guide at http://www.ttmsolutions.com
>
>
>
>
> Ben Amitai wrote:
>>
>> Hello,
>> My application has one and only broker. I don't need the broker to
>> discover other brokers.
>> Is there a way to disable the discoverying entir
7;t need the broker to
>> discover other brokers.
>> Is there a way to disable the discoverying entirly?
>>
>> Thanks
>> Udi
>>
>
>
--
View this message in context:
http://www.nabble.com/Disable-multicast-discovery-tp21132232p21132579.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
but I can see
> a thread of 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.
>
>
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
nly broker. I don't need the broker to
> discover other brokers.
> Is there a way to disable the discoverying entirly?
>
> Thanks
> Udi
>
--
View this message in context:
http://www.nabble.com/Disable-multicast-discovery-tp21132232p21132399.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
properties, but I can see
a thread of 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.
Hello,
My application has one and only broker. I don't need the broker to discover
other brokers.
Is there a way to disable the discoverying entirly?
Thanks
Udi
--
View this message in context:
http://www.nabble.com/Disable-multicast-discovery-tp21132232p21132232.html
Sent from the Act
tried
really hard but just couldn't find any 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.
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
> >&
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?
&g
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
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 th
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 listener
; wrote:
>
> 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
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 fa
im
> >
> > 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 (Pro
;>
>> 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
>> > discoveryUri="multicast://prod1"/>
&
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) -> B
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
Client 2 (Consumer) -> Broker 2
But I am not sure how to configure the client side. this is what I have.
Cl
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
55 matches
Mail list logo
