[
https://issues.apache.org/jira/browse/AMQ-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15329597#comment-15329597
]
Christopher L. Shannon commented on AMQ-6323:
---------------------------------------------
Fix applied
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=a953f11d0e6e4f271e99f1b9ac6cfb01ee0ecf99
> Support reduceMemoryFootprint flag for Topics
> ---------------------------------------------
>
> Key: AMQ-6323
> URL: https://issues.apache.org/jira/browse/AMQ-6323
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 5.13.3
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Fix For: 5.14.0
>
>
> Currently the {{reduceMemoryFootprint}} flag exists on a policy and can be
> used for Queues but not for Topics. While the flag can be set for Topics, it
> doesn't get applied anywhere. We should be able to apply this flag for
> persistent messages just like we do for Queues so that the state can be
> cleared after the message has been marshalled to a byte sequence. This will
> allow the broker to save memory and help prevent OOM errors because the
> memory usage counter only tracks the marshalled state of the message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
