[
https://issues.apache.org/jira/browse/ARTEMIS-3778?focusedWorklogId=756603&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-756603
]
ASF GitHub Bot logged work on ARTEMIS-3778:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Apr/22 18:44
Start Date: 13/Apr/22 18:44
Worklog Time Spent: 10m
Work Description: clebertsuconic opened a new pull request, #4029:
URL: https://github.com/apache/activemq-artemis/pull/4029
Instead of holding a thread and an iterator, we should instead keep moving
to next references
without holding any threads. Just with callbacks.
Issue Time Tracking
-------------------
Worklog Id: (was: 756603)
Remaining Estimate: 0h
Time Spent: 10m
> 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: 10m
> 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)
