[
https://issues.apache.org/jira/browse/ARTEMIS-4206?focusedWorklogId=855102&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855102
]
ASF GitHub Bot logged work on ARTEMIS-4206:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 05/Apr/23 16:52
Start Date: 05/Apr/23 16:52
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #4418:
URL:
https://github.com/apache/activemq-artemis/pull/4418#issuecomment-1497822645
I can squash 2 commits in one for two different and related issues. I
thought it was better to keep separated.
Regarding the trace. I think it's better this way. Say an user starts
having issues if we just set the logger we would get what we need.
Issue Time Tracking
-------------------
Worklog Id: (was: 855102)
Time Spent: 5h 20m (was: 5h 10m)
> 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 20m
> 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)
