activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (AMQ-6811) ReduceMemoryFootprint does not work on messages with no body
Date Fri, 15 Sep 2017 14:13:00 GMT


ASF subversion and git services commented on AMQ-6811:

Commit f82993d9c2315d7ea6c35d164f7665987cdbe1b8 in activemq's branch refs/heads/master from
[;h=f82993d ]

AMQ-6811 - fix reduceMemoryFootprint when no message body

ReduceMemoryFootprint will now properly detect that a message is
marshalled even if there is no message body so the headers can be
cleared out after message send

> ReduceMemoryFootprint does not work on messages with no body
> ------------------------------------------------------------
>                 Key: AMQ-6811
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.15.0
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>             Fix For: 5.15.1, 5.16.0
> I was debugging an out of memory error on a broker that was caused by the unmarshalled
message properties being in memory even though the reduceMemoryFootprint flag was set to true
so this map should have been cleared after send.  
> Upon further investigation I realized it was because the isMarshalled() method on a message
only checks if the marshalled content is not null however the check should actually be if
the content is not null OR if the unmarshalled value is null/empty (ie no body set at all).
 This same check is already done properly for header properties and just needs to be extended
for the body.

This message was sent by Atlassian JIRA

View raw message