Hello, We’re using Artemis 2.20. We had a misbehaving application that had been opening consumers without closing them which I recently addressed. The fix was deployed today and since then I have been seeing a lot of the following error (as the consumer count is very slowly trickling down)
2022-04-13 08:54:42,957 ERROR [org.apache.activemq.artemis.core.server] AMQ224013: failed to expire messages for queue: java.util.concurrent.TimeoutException: UpdateOutboundRetry at org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl$ExpiryReaper.run(PostOfficeImpl.java:1861) [artemis-server-2.20.0.jar:2.20.0] at org.apache.activemq.artemis.core.server.ActiveMQScheduledComponent.runForExecutor(ActiveMQScheduledComponent.java:313) [artemis-commons-2.20.0.jar:2.20.0] at org.apache.activemq.artemis.core.server.ActiveMQScheduledComponent.lambda$bookedRunForScheduler$2(ActiveMQScheduledComponent.java:320) [artemis-commons-2.20.0.jar:2.20.0] at org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42) [artemis-commons-2.20.0.jar:] at org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31) [artemis-commons-2.20.0.jar:] at org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:65) [artemis-commons-2.20.0.jar:] at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [java.base:] at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [java.base:] at org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118) [artemis-commons-2.20.0.jar:] Just wondering if these errors cause any lasting damage, and if it means that something is not tuned correctly, or is a normal part of recovering from such a severe leak (we had hundreds of thousands of stale consumers on that queue.) Stephen E Baker
