The logic for detecting and dealing with slow consumers is in
org.apache.activemq.artemis.core.server.impl.QueueImpl.SlowConsumerReaperRunnable
[1]. Right now it doesn't deal with the use-case you've described.
Contributions are always welcome.
Justin
[1]
https://github.com/apache/activemq-arte
I have a project working on ActiveMQ. And I plan to migrate it to Artemis.
Therefore, on the test environment, I installed Artemis and get a situation
where the messages in one or the other queue "hang." This happens two to
three times a day in a random order and requires manual actions.
In this re
Are messages being added to the queue at a rate of 10 per second? If not,
the algorithm will take that into account and it won't close consumers
because in situations like that every consumer would be disconnected with
message production slows down which is generally not desirable.
Also, consumer
