[jira] [Commented] (ARTEMIS-3067) AMQP applicationProperties are not part of the memoryEstimate

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

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

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

Commit d186d204063f85899eada811336caf077f26ecb7 in activemq-artemis's branch refs/heads/master from gtully
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=d186d20 ]

ARTEMIS-3067 - track application properties in memory estimate and check for modification after potential filter execution


> AMQP applicationProperties are not part of the memoryEstimate
> -------------------------------------------------------------
>
>                 Key: ARTEMIS-3067
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3067
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 2.16.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Major
>             Fix For: 2.17.0
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> With significant data in application properties, the decoded properties can consume memory that is not tracked for paging purposes and can lead to unexpected OOM.
> Duplicate detection is one cause of decoding. Use of selectors is another. Otherwise they are left intact by the broker and just routed in their raw format.
> When they are decoded, for whatever reason, we need to account for them is some way such that paging can kick in as expected.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)