Queues named like "$.artemis.internal.sf." are internal queues used to move messages between nodes for things like server-side message load-balancing or message redistribution. As long as the cluster is formed properly then messages should not accumulate there but should land there for just a moment before they are moved across the cluster bridge to the other node. I would expect the "Messages Added" stat to go up, but I would expect the "Message Count" to stay close to 0.
Are you seeing any functional impact? Justin On Thu, Sep 21, 2017 at 6:03 AM, gkocur <grzegorz.ko...@softwaremill.com> wrote: > Hello, > > I have a newbie question. > I'm playing with artemis clustering, and have simple setup like this: > > pruducer----artemis-server1----consumer1 > | > artemis-server2----consumer2 > > Messages are balanced to server2 exactly as described in documentation. The > only issue I have with this setup is message acknowledgement - "Message > count" for queue > "$.artemis.internal.sf.ersules.f2a284aa-9c3b-11e7-96f2-062013112720" (so > sent to server2) is growing, and "Messages acknowledged" is always 0. Is it > expected behaviour? Or do I miss some configuration? > > Thank you for any help with this. > > -- > Grzegorz > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
