You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2016/03/22 16:48:25 UTC
[jira] [Created] (AMQ-6222) Message content can be cleared by
mistake when isReduceMemoryFootprint is enabled
Christopher L. Shannon created AMQ-6222:
-------------------------------------------
Summary: Message content can be cleared by mistake when isReduceMemoryFootprint is enabled
Key: AMQ-6222
URL: https://issues.apache.org/jira/browse/AMQ-6222
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.13.2
Reporter: Christopher L. Shannon
Assignee: Christopher L. Shannon
In a Queue when isReduceMemoryFootprint is enabled the message state should be cleared after persisting to the store. The idea is that once the data is marshalled into its byte content we can clear out the properties, text, etc to free up memory.
The problem is that when concurrent dispatch is enabled, messages are added to the store asynchronously and queued up. There is a race condition because it's possible for the state to be cleared before the store has a chance to process the message so that when it gets to it, it will be null. This is most notable when using the VM transport as messages with null content will get dispatched.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)