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 both
Hi there,
I have a setup of 10 brokers networked together using Network of Brokers.
Recently, after upgrading I start getting the following logs repeatedly:
2023-04-06 16:32:00,710 | WARN | TopicSubscription:
consumer=localhost->localhost-52655-1680710609766-1675:1:1:1, destinations=461,
disp
between the sites? I
have a broker on each site with a network bridge between them. I know that
creating a conduit network connector won't work as selectors are disregarded
but wondered if there is another solution?
Any help is much appreciated.
Many thanks
Paul Burgess
Hi all,
Do we know roughly when 5.16.4 will be released?
Sorry if you've answered this already, I couldn't find it in any of the recent
threads.
Thanks
lover
transport in NoB configuration, so my memory is rusty.
Tim
On Tue, Nov 2, 2021, 6:58 AM Paul Burgess wrote:
> Hi Tim,
>
> Thank for the additional info. I actually use the failover transport
> regularly for clients, so am aware of the priorityBackup option - thanks
> all
ority Backup section of
https://activemq.apache.org/failover-transport-reference.html) to get the
behavior of failing back to the fast link when it becomes available once
again.
I'm very surprised to hear that the masterslave transport is available but
the failover transport is not. Can
en with more
brokers the fast links will have "higher" priority.
the other option is to use a single bridge with two urls
failover:(fast-link,slow-link)?randomize=false and the slow link will
only be used on failure of the fast link.
hope this helps!
On Mon, 1 Nov 2021 at 16:57,
and fallback to remote brokers else.
Is it what you are looking for ?
Regards
JB
> Le 1 nov. 2021 à 17:37, Paul Burgess a écrit :
>
> Hi,
>
> I'm trying to configure a network of brokers, where links between the brokers
> work as a 'Primary' and 'Second
Hi,
I'm trying to configure a network of brokers, where links between the brokers
work as a 'Primary' and 'Secondary/Failover' pair, much like failover transport
connections and priority URIs.
I have links between sites that are fast and stable, that I want to be used as
a priority, with a bac
