Just out of coincidence, without even reading this thread.. I had
opened this JIRA and Pull Requests:
https://issues.apache.org/jira/browse/ARTEMIS-3778
https://github.com/apache/activemq-artemis/pull/4029
Feedback is welcomed since you're hitting the warning... it's pretty
much removing the
The exception is just indicating that the expiration task didn't finish in
the hard-coded 10 second allotment of time. There is no "damage" lasting or
otherwise. The expiry reaper scans the messages in the queue for any that
have expired. I wouldn't expect the number of consumers on that queue to
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)
Hi Tim,
Thanks for responding. We are able to resolve the issue by creating connection
and session for each queue separately later the error stopped coming in the
consumer.
NMS client with single connection and single session with transaction to
consume from multiple queues is not working
This isn't something I've seen reported for non-NMS clients, and it's my
understanding that the NMS client gets a lot less use than the JMS client
so it's entirely possible that there's a bug in the NMS client that no one
has detected till now.
Are you able to reproduce this reliably? If so,
