Hello,
Is there any way to specify which queues/topics to include and/or exclude from
AMQP Mirroring?
Thank you,
Aaron Steigerwald
Hello,
Should empty auto-created queues and/or topics persist broker restarts with
this setting?-
false
...
It doesn't seem to in 2.21.0. Setting
false seems to persist
auto-created addresses but empty auto-created queues and topics are still
deleted.
Also, setting false seems to pre
I think it was ignorable, but I'm dealing with it:
https://github.com/apache/activemq-artemis/pull/4049/commits/952bfde37d79701a02f6626c6345447d5fcd3e20
It should be part of the release this week
On Mon, Apr 25, 2022 at 11:17 AM Clebert Suconic
wrote:
>
> it means the message was not found...
I've given up reproducing this NPE for now. At this point can you confirm
that the PR [1] fits your needs? If so, I can merge it and it can be
included in the next release which should be started in the next few days.
Justin
[1] https://github.com/apache/activemq-artemis/pull/4021
On Wed, Apr 2
I opened ARTEMIS-3801 [1] and sent a PR to fix what was broken.
However, it's worth noting that your code will still not work as it did
before because the previous behavior violated the MQTT 3.1.1 specification.
As noted previously, both MQTT 3.1.1 and 5 specifications contain
MQTT-4.7.2-1 which s
I've reproduced this problem and I'm investigating. At first glance it
appears related to the implementation of MQTT-4.7.2-1 which states:
> The Server MUST NOT match Topic Filters starting with a wildcard
character (# or +) with Topic Names beginning with a $ character.
This is part of both MQTT
Thank you Justin,
I managed to reproduce what you suggested, using FQDN with STOMP and its
synthax for special characters like ":"
/send SUBSCRIBE\ndestination:myAddress\\c\\cmyQueue\n\n\0
Nicolas
C2 - Usage restreint
-Message d'origine-
De : Justin Bertram
Envoyé : lundi 25 avril
As you observed, the queue automatically created for a non-durable
subscription for a STOMP client is not named according to the client-id. It
uses a UUID which means the name is non-deterministric and therefore can't
be readily shared across multiple clients. However, you should be able to
use FQQ
it means the message was not found... probably a target came to remove
it.. while the message itself was also being removed.
On Wed, Apr 20, 2022 at 12:27 PM Stephen Baker
wrote:
>
> I was purging ExpiryQueues and I noticed the following warning in our Artemis
> logs.
>
> We have a dual mirror s
Any configurations to reduce the time for backup server to be active when
primary (master) server was isolated from network? During the test when the
network card in primary Artemis server was disabled (primary server was
isolated from network), it took 90 - 120 seconds for the backup server to
> My hope is a more streamlined way exists.
It should not be too difficult to create an alternative GUI in which you can
select a broker instance.
But is that approach sufficient? Or do you require an integrated view for an
Artemis cluster? e.g. list all connections for a cluster of brokers?
I h
The ActiveMQ Artemis web console can only manage one broker at a time. To
my knowledge there are no tools to manage multiple brokers simultaneously
in real-time. There are, of course, tools to manage and deploy broker
configurations behind-the-scenes so to speak (e.g. Ansible, Puppet, etc.).
Just
Hello,
I managed to successfully create a shared durable subscription using a
"client-id" and a "durable-subscriber-name" with the STOMP protocol.
However, always with STOMP, I can't find a way to create a shared non-durable
subscription. When I set only the "client-id", it does not seem to be
13 matches
Mail list logo
