[jira] [Commented] (ARTEMIS-4206) Unreferenced AMQP Large Messages are not removed

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on ARTEMIS-4206:
----------------------------------------------------------

Commit 6d3dbc438389222ccaadba70ae8640b1fb0309da in activemq-artemis's branch refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=6d3dbc4383 ]

ARTEMIS-4233 Large Message Issues After Failed Clients

- interrupted message breaking reference counting
After the server writing to the client is interrupted in AMQP, the reference counting was broken what would require the server restarted
in order to cleanup the files of any interrupted sends.

- Removed consumer during large message delivery damaging large messages
If the consumer failed to deliver messages for any reason, the message on the queue would be duplicated. what would wipe out the body of the message
and other journal errors would happen because of this.

extra debug capabilities added into RefCountMessage as part of ARTEMIS-4206 in order to identify these issues


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