[
https://issues.apache.org/jira/browse/ARTEMIS-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612759#comment-17612759
]
ASF subversion and git services commented on ARTEMIS-4024:
----------------------------------------------------------
Commit 23d6f19080835c57d917375ca1e5d16afe31fe43 in activemq-artemis's branch
refs/heads/2.21.0.jbossorg-x from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=23d6f19080 ]
ARTEMIS-4024 Avoid excessive NativeMemory allocation when sending OpenWire
Multi mega sized messages in openwire
(cherry picked from commit 18cfdb7049ca90e5c5a08611413f6ba5d60152ff)
(cherry picked from commit 20fde76e99c040abafe6aecd8c22ddcb201fd8a4)
downstream: ENTMQBR-7204
> Avoid excessive NativeMemory allocation when sending OpenWire Multi mega
> sized messages in openwire
> ---------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-4024
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4024
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> when sending a large message in openwire, we will read the entire file on the
> memory, make the conversion from core, and send it on net
> throughOpenWireProtocolManager::sendPhisical.
> Such allocation should be limited and be sent in chunks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
