[ 
https://issues.apache.org/jira/browse/ARTEMIS-4206?focusedWorklogId=853818&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-853818
 ]

ASF GitHub Bot logged work on ARTEMIS-4206:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 30/Mar/23 03:02
            Start Date: 30/Mar/23 03:02
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on PR #4418:
URL: 
https://github.com/apache/activemq-artemis/pull/4418#issuecomment-1489616826

   I have been debugging with these messages, and I am making a few adjustments 
(Missed debug statements... etc)... this is being useful in a scenario where 
the Cpu Is overloaded and everything is failing on the delivering, leaving 
messages behind.
   
   it is working as I expected to tell me what is happening, but I'm making a 
few adjustments.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 853818)
    Time Spent: 2.5h  (was: 2h 20m)

> 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: 2.5h
>  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)

Reply via email to