[
https://issues.apache.org/jira/browse/ARTEMIS-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17084264#comment-17084264
]
Robbie Gemmell commented on ARTEMIS-2712:
-----------------------------------------
I've attached a modified Proton Python helloworld that I used to confirm the
issue did exist exactly as it looked it would. Its a not a great example of it
as it just ends up with 2 full message payloads munged together, but it works.
Running "PN_TRACE_FRM=1 ./helloworld.py" (with Proton Python available / built
/ installed) and looking at the transfer frame received at the consumer shows
fairly obviously whether the content was corrupted. Pre-testing a change
Clebert is working on showed the issue was resolved by the change.
> updated large message handling not accounted for in aborted message cleanup
> ---------------------------------------------------------------------------
>
> Key: ARTEMIS-2712
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2712
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.12.0
> Reporter: Robbie Gemmell
> Priority: Blocker
> Attachments: helloworld.py
>
>
> ARTEMIS-1975 updated the message handling for 'larger' AMQP messages, but in
> doing so introduces additional behaviours while handling such messages. These
> dont appear to have been similarly catered for during aborted message cleanup
> (irony: those being more likely for this to be needed). As such it currently
> looks like message corruption could occur if a subsequent message arrived
> after an abort.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
