You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Clebert Suconic (Jira)" <ji...@apache.org> on 2022/10/03 13:59:00 UTC

[jira] [Commented] (ARTEMIS-4024) Avoid excessive NativeMemory allocation when sending OpenWire Multi mega sized messages in openwire

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

Clebert Suconic commented on ARTEMIS-4024:
------------------------------------------

this is a borderline of an enhancement and a bug... I will keep it categorized as bug just from the user's perspective (sending an openWire sized as 200MB would cause the broker to exhaust DirectMemory usage and get OMEs when sending messages). 

from my POV is an enhancement as this was not supposed to happen.. but I will keep the user's POV here.

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