ess wrote:
>
> Hello,
>
> I have a scenario where messages are failing to propagate over a network
> connector between two brokers.
>
> My scenario has been simplified for the purpose of diagnosis. I have 2
> brokers with 2 network connectors between them going one way
Hello,
I have a scenario where messages are failing to propagate over a network
connector between two brokers.
My scenario has been simplified for the purpose of diagnosis. I have 2 brokers
with 2 network connectors between them going one way, utilising two physical
connections to achieve
sockets ("wss://"). The reverse proxy will connect towards its
> ActiveMQ via TPC. The documentation calls this scenario a network of
> brokers. The examples only show configurations with a TCP connection. It
> does mention (https://activemq.apache.org/networks-of-brokers) that oth
scenario a network of
brokers. The examples only show configurations with a TCP connection. It
does mention (https://activemq.apache.org/networks-of-brokers) that other
connections (network connectors) are possible. In a book, I have seen that a
connection with a reverse proxy inbetween two Ac
Great, thanks for sharing the code in case someone else has the same
question in the future.
Tim
On Tue, May 22, 2018, 11:37 PM maorbl wrote:
> Just wanted to update that eventually I added the network connectors
> not with the proxy (BrokerViewMBean), but with the broker
Just wanted to update that eventually I added the network connectors
not with the proxy (BrokerViewMBean), but with the broker itself
(BrokerService).
This is the code that adds a new network connector (similar to how
activemq code handles a new network connector):
NetworkConnector
Hi Tim,
Thanks a lot for your answer!
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
ement.InstanceAlreadyExistsException:
> org.apache.activemq:type=Broker,brokerName=ig2-1,
> connector=networkConnectors,networkConnectorName=NC
> at com.sun.jmx.mbeanserver.Repository.addMBean(
> Repository.java:437)
>
> I understand that it fails on InstanceAlreadyExistsExceptio
ails on InstanceAlreadyExistsException, but I don't
know
how to overcome it.
A workaround is to remove the fist network connector
proxyBroker.removeNetworkConnector("NC");
and then add both network connectors:
proxyBroker.addNetworkConnector("static://"+urlBroker2+",&
In the event of connection failures there is a good chance of loosing
messages.
If you are about messages and replies then use real queues, maybe have a
reply queue per process or per application and use selectors based on the
correlation id if you need to multiplex.
The lifetime of a temp queue i
In any mesh network, I'd always recommend setting
decreaseNetworkConsumerPriority=true. If you do that, and if clients will
only ever connect to a single broker, then a networkTTL of 2 is fine,
because the message will always traverse at most two brokers.
However, if your consumers can disconnect
We are using n/w connectors between 3 brokers
is
A->B
A->C
B->A
B->C
C->A
C->B
also we are using synchronous request and reply pattern using camel to send
and receive message in temp queue.
we have question is it good to use networkTTL = 2 in above configuration ?
will it work properly or
is
Hello Tim,
Thank you for your reply ..
Yes my brokers are embedded and the process gets notified of new servers
which come up. Once i wrote the question i did try it out and could see via
jmx that the network connector started working and showed up. However i
still need to get it working perfectl
broker's network configuration to already started BrokerService ?
>>
>> In ActiveMQ API what I mean is
>>
>> BrokerService broker = new BrokerService();
>> // some activemq configuration
>> ...
>> ...
>> broker.start()
>>
>> broker.addNetworkConnecto
>
> In ActiveMQ API what I mean is
>
> BrokerService broker = new BrokerService();
> // some activemq configuration
> ...
> ...
> broker.start()
>
> broker.addNetworkConnector("static:(tcp://10.x.x.x:62001)").start(); //
> not
> sure if this would
configuring all
possible network connectors up front.
Thank you!
Regards,
-Yogesh
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
priorityBackup works with networkConnectors.
>
> On Thu, Oct 30, 2014 at 5:53 AM, Gary Tully wrote:
>
> > you may be able to achieve what you want with two network connectors. one
> > to the primary and one to the backup. When both are alive and you use
> > decreaseNetworkC
to achieve what you want with two network connectors. one
> to the primary and one to the backup. When both are alive and you use
> decreaseNetworkConsumerPriority and priority dispatch, messages should take
> the shortest path (priority decreases with number of hops).
>
> On 24 October 20
you may be able to achieve what you want with two network connectors. one
to the primary and one to the backup. When both are alive and you use
decreaseNetworkConsumerPriority and priority dispatch, messages should take
the shortest path (priority decreases with number of hops).
On 24 October
tivemq/blob/d54e0d6ab590b6a6148a5e2629c45b95d3f40eb8/activemq-client/src/main/java/org/apache/activemq/transport/discovery/simple/SimpleDiscoveryAgent.java#L42
>> > > > >
>> > > > > The network bridge is a discovery listener, it gets told to
>> > add/remove
>> > > > > services (urls
o
> > add/remove
> > > > > services (urls) that are discovered/retried.
> > > > >
> > > > >
> > > > > On 24 September 2014 20:20, Tim Bain
> wrote:
> > > > >
> > > > > > Gary, Torsten, and othe
> > >
> > > > > Gary, Torsten, and others have said in various places that
> > > > broker-to-broker
> > > > > networkConnectors should set maxReconnectAttempts=0 to allow
> > > reconnection
> > > > > to be handled by the network bridge. (S
w
> > reconnection
> > > > to be handled by the network bridge. (Sources: 1
> > > > <
> > > >
> > >
> >
> http://tmielke.blogspot.com/2011/09/activemq-network-bridge-to-masterslave.html
> > > > >,
> > > > 2
> > &
t;,
> > > 2
> > > <
> > >
> >
> http://activemq.2283324.n4.nabble.com/Persistent-messages-disappearing-td4681353.html
> > > >,
> > > 3
> > > <
> > >
> >
> http://grokbase.com/t/activemq/users/1427v9eq
t; > 2
> > <
> >
> http://activemq.2283324.n4.nabble.com/Persistent-messages-disappearing-td4681353.html
> > >,
> > 3
> > <
> >
> http://grokbase.com/t/activemq/users/1427v9eqkf/prioritybackup-not-supported-with-masterslave
> > >)
>
27v9eqkf/prioritybackup-not-supported-with-masterslave
> >)
> Torsten (link 1) was talking about static: network connectors, while Gary's
> quotes in the other two links were related to failover: (or masterslave:,
> which is just chrome on top of failover:), but if it's a requ
<http://activemq.2283324.n4.nabble.com/Persistent-messages-disappearing-td4681353.html>,
3
<http://grokbase.com/t/activemq/users/1427v9eqkf/prioritybackup-not-supported-with-masterslave>)
Torsten (link 1) was talking about static: network connectors, while Gary's
quotes in the other tw
I need to implement scaling(Horizontal ,vertical) and broker to broker
communication network connectors in activemq .Actually we are using vm
broker url in the xml file. After I gone through activemq documents I came
to know peer protocol functionality is similar to vm protocol for
establishing
t;
> The alternatives here are by keeping track of the status in my Transport
> Listener or by parsing the logs (which is a very undesirable alternative).
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Trasport-Listener-for-embedded-broke
tener-for-embedded-broker-network-connectors-tp4654830p4654866.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
clared in the embedded broker pointing to the stand alone broker?
>
> Thanks,
>
> Claudio
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Trasport-Listener-for-embedded-broker-network-connectors-tp4654830.html
> Sent from the A
sport Listener to the Network Connector
declared in the embedded broker pointing to the stand alone broker?
Thanks,
Claudio
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Trasport-Listener-for-embedded-broker-network-connectors-tp4654830.html
Sent from the ActiveMQ - User ma
t;>
>> https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-optional/src/test/java/org/apache/activemq/bugs/AMQ2764Test.java?hb=true
>>
>> tests network connectors over http scenario. Of course, you should test
>> your use case.
>>
>> Regards
>&
s://fisheye6.atlassian.com/browse/activemq/trunk/activemq-optional/src/test/java/org/apache/activemq/bugs/AMQ2764Test.java?hb=true
>
> tests network connectors over http scenario. Of course, you should test
> your use case.
>
> Regards
> --
> Dejan Bosanac - http://twitter.com/dejanb
>
Yes,
https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-optional/src/test/java/org/apache/activemq/bugs/AMQ2764Test.java?hb=true
tests network connectors over http scenario. Of course, you should test
your use case.
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
Just to be clear, we could ship software containing an embedded or
standalone broker that is told to connect to (for argument's sake)
https://broker1.mycompany.com:61616 and
https://broker2.mycompany.com:61616and it will form part of the broker
network allowing clients to connect
locally?
James
O
You can use http transport inside you network connector, no problem about
that.
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource.com
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www
Hi,
The network connector is documented with tcp:// transport. Are there others?
For instance, imagine I want to install a broker that is behind a
customer's firewall, and connect it to a production network of brokers.
HTTP/S might be allowed by the customer for outbound connections but
nothing e
..
--
View this message in context:
http://old.nabble.com/AMQpersistence-store-and-network-connectors-tp28839202p28839202.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hello,
possible to know how could you configure your network connector for
default: network connectors included destination Caracteristicas: A. only *
for all network connectors are all A broker, only B *, for all network
connectors on all B brokers.
Thank you in advance
Best regards,
titexe
Hi folks,
in a hub&spoke scenario where:
1\ both the hub broker and the spoke brokers are secured
2\ each spoke broker uses a duplex network connector to establish a two way
msg exchange w/hub
I understand from
http://cwiki.apache.org/confluence/display/ACTIVEMQ/Security that the
network connec
Thank you for your very quick answer !
Eric-AWL
rajdavies wrote:
>
>
> On 31 Jul 2009, at 08:21, Eric-AWL wrote:
>
>>
>> Hi
>>
>> Is it possible and allowed (it's important for us to respect
>> evolutivity) to
>> dynamically chang
On 31 Jul 2009, at 08:21, Eric-AWL wrote:
Hi
Is it possible and allowed (it's important for us to respect
evolutivity) to
dynamically change the network connectors caracteristics (ex :included
destinations, and excluded destinations), without restarting the
embedded
broker ?
Ex :
Hi
Is it possible and allowed (it's important for us to respect evolutivity) to
dynamically change the network connectors caracteristics (ex :included
destinations, and excluded destinations), without restarting the embedded
broker ?
Ex : Site A, Site B
queues : A.queue1, B.queue1, A.q
We don't support multiple directional connections between two brokers
- i.e.
We support:
--->
AB
<---
but not
>
A B
--->
--
View this message in context:
http://www.nabble.com/Defining-Multiple-Network-Connectors-in-a-Network-of-Brokers-
e set up
multiple connections between two brokers? The documentation
indicates that
defining multiple network connectors in the broker configuration
should
achieve this, but we seem to be unable to correctly configure this.
Again, using Broker A and Broker B as the two brokers, I’ve tried
the
follow
All,
Another question on Network of Brokers. How exactly does one set up
multiple connections between two brokers? The documentation indicates that
defining multiple network connectors in the broker configuration should
achieve this, but we seem to be unable to correctly configure this.
Again
47 matches
Mail list logo
