[
https://issues.apache.org/jira/browse/ARTEMIS-4206?focusedWorklogId=855139&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855139
]
ASF GitHub Bot logged work on ARTEMIS-4206:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 05/Apr/23 20:25
Start Date: 05/Apr/23 20:25
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #4418:
URL:
https://github.com/apache/activemq-artemis/pull/4418#issuecomment-1498100344
The idea of this feature is to be a hidden feature...
So, I am going to use the following logger to enable this type of debugging:
private static final Logger refLogger =
LoggerFactory.getLogger(MethodHandles.lookup().lookupClass().getName() +
".REF_DEBUG");
Issue Time Tracking
-------------------
Worklog Id: (was: 855139)
Time Spent: 5h 50m (was: 5h 40m)
> Unreferenced AMQP Large Messages are not removed
> ------------------------------------------------
>
> Key: ARTEMIS-4206
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4206
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Fix For: 2.29.0
>
> Time Spent: 5h 50m
> Remaining Estimate: 0h
>
> Say you crashed the server after the ack, and before the file.remove, and the
> journal. record removal.
> The AMQP Large Message may not be removed right away, requiring a restart of
> the broker.
> At this point this is really caused by ARTEMIS-4193 and only affected 2.29.0
> and no previous versions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
