[
https://issues.apache.org/jira/browse/ARTEMIS-3778?focusedWorklogId=756968&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-756968
]
ASF GitHub Bot logged work on ARTEMIS-3778:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 14/Apr/22 13:45
Start Date: 14/Apr/22 13:45
Worklog Time Spent: 10m
Work Description: gemmellr commented on code in PR #4029:
URL: https://github.com/apache/activemq-artemis/pull/4029#discussion_r850461538
##########
artemis-server/src/main/java/org/apache/activemq/artemis/core/server/impl/QueueImpl.java:
##########
@@ -2454,10 +2450,10 @@ public void run() {
if (doneCallback != null) {
doneCallback.run();
- doneCallback = null;
}
}
+
Review Comment:
I wouldnt say this comment still applies. It seems strange to log that it is
"done" in the cases it has just been logged that it isnt finished.
Issue Time Tracking
-------------------
Worklog Id: (was: 756968)
Time Spent: 1h (was: 50m)
> Reaper reporting TimeoutException on Reaper threads
> ---------------------------------------------------
>
> Key: ARTEMIS-3778
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3778
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.21.0
> Reporter: Clebert Suconic
> Priority: Major
> Fix For: 2.22.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> If a queue is holding too many references, and it takes more than 10 seconds
> to iterate on references, the reaper will log an error:
> AMQ224013: failed to expire messages for queue:
> java.util.concurrent.TimeoutException
> Instead I should streamline reaping to resume the next queue when one queue
> is done. This way no thread is held blocking and we just streamline the
> process.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
