A queue with a name like "35d32888-b22a-4489-98ee-d0de7a0d6312" is almost certainly a temporary queue (e.g. used for a JMS or MQTT topic subscription). These queues don't survive a broker restart so it's not terribly surprising you'd get some warnings like this.
In any case, can you clarify which node you restarted (i.e. the mirror source and the target) and on which node you're seeing these messages (i.e. the mirror source or the target)? Justin On Fri, Jan 31, 2025 at 5:35 AM Kamara, George (RWS CIV) <george.kama...@rws.nl.invalid> wrote: > Firstly, I hope I am taking the correct approach to requesting support. > > I have artemis 2.39.0 running on Kubernetes with two statefulsets, > non-clustered but mirrored which works well enough for my requirements. > However: when I upgrade/or restart one of the pods, my logs are flooded > with > > 2025-01-31 12:24:00,147 WARN > [org.apache.activemq.artemis.protocol.amqp.connect.mirror.AMQPMirrorControllerTarget] > Queue 35d32888-b22a-4489-98ee-d0de7a0d6312 not found on mirror target, > ignoring ack for queue=35d32888-b22a-4489-98ee-d0de7a0d6312, > messageID=533235, nodeID=1d9ddecf-dfb3-11ef-8af4-2232a8ed0c9e > > I understand this is a standard message to show there are differences > between the two nodes. > > My question is what’s the best way to handle this situation. Is this OK to > ignore or is there something I should be proactively doing? > > Thanks in advance. > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org > For additional commands, e-mail: users-h...@activemq.apache.org > For further information, visit: https://activemq.apache.org/contact > >
