you should always receive messages from the point you create a queue on...
you are probably removing the queue with auto-delete? I'm looking to
disable auto-delete on auto created queues.. as I have seen many
questions around it. can you take a look if you are deleting a queue
that was auto-creat
What does "include all destinations in the 5.3 -> 5.16 direction, to force
all messages to be transferred" entail?
On Fri, Jun 4, 2021, 5:45 AM Tim Bain wrote:
> One option would be to load the 5.3 data file into a new temporary 5.3
> broker and configure it to make a network of brokers with you
Edson,
> Am I correct on supposing it is possible to have 2 bakckups for one master?
You can have as many backup nodes as you want or need.
But each master node will accept only one backup node during operation.
The second backup node will remain idle until the first backup node is somehow
gone.
Hi!
I’m trying to setup a cross DC setup with one master and two slaves.
Servers are:
Sc0b03 => master
Pr0b03 => slave 1
Sp0b03 => slave 2
The relevante configuration is:
On Master server:
tcp://sc0b03:61616
tcp://pr0b03:61616
tcp://sp0b03:61616
xx
OK, thanks for clarifying the root cause.
Tim
On Thu, Jun 3, 2021, 12:10 AM ヤ艾枫o.-- <1169114...@qq.com> wrote:
> Hi
>
>
>
> writing problem, the setting expiration time is very short (1 second).
>
> But in the actual verification, I used 10 seconds。
> The reason for this problem
One option would be to load the 5.3 data file into a new temporary 5.3
broker and configure it to make a network of brokers with your 5.16.0
broker. You'll likely want to statically include all destinations in the
5.3 -> 5.16 direction, to force all messages to be transferred to the
5.16.0 broker.
Good afternoon all!
Artemis version: 2.17.0
This week I ran into a behavior of Artemis that I did not expect nor fully
understand so I hope that with this e-mail someone is able to point me to the
relevant documentation.
TL;DR:
Say we have a durable queue configured connected as multicast to t
