You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Clebert Suconic (Jira)" <ji...@apache.org> on 2022/04/28 15:15:00 UTC

[jira] [Closed] (ARTEMIS-3778) Reaper reporting TimeoutException on Reaper threads

     [ https://issues.apache.org/jira/browse/ARTEMIS-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clebert Suconic closed ARTEMIS-3778.
------------------------------------
    Resolution: Fixed

> 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: 2h
>  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.7#820007)