[
https://issues.apache.org/jira/browse/ARTEMIS-4206?focusedWorklogId=855243&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855243
]
ASF GitHub Bot logged work on ARTEMIS-4206:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 06/Apr/23 09:39
Start Date: 06/Apr/23 09:39
Worklog Time Spent: 10m
Work Description: gemmellr commented on PR #4418:
URL:
https://github.com/apache/activemq-artemis/pull/4418#issuecomment-1498773294
> 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");
It will certainly be hidden, people will enable it without knowing they are
since it is a descendent in the regular class name logger hierarchy. Anyone
simply enabling debug logging for the class (or more likely, many classes /
further up the hierarchy) will get the change in actual system behaviour of the
ref counting debug and saving lots of stacktraces. They would have to know
about the change in behaviour and reconfigure the specific ref count logger
back off in order to restore the prior behaviour and only add debug output for
the normal system behaviour.
Issue Time Tracking
-------------------
Worklog Id: (was: 855243)
Time Spent: 6h 10m (was: 6h)
> 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: 6h 10m
> 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)
