[
https://issues.apache.org/jira/browse/AMQ-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458717#comment-13458717
]
Bruce Snyder commented on AMQ-3643:
-----------------------------------
Correct, the VM transport has never bothered to check for available memory
before adding messages. To fix this bug, the {{VMPendingMessageCursor}} needs
to be refactored to utilize the methods for this in the
{{AbstractPendingMessageCursor}} so that it obeys the
{{memoryUsageHighWaterMark}} property.
> vmQueueCursor does not honour system wide memoryUsage limit
> -----------------------------------------------------------
>
> Key: AMQ-3643
> URL: https://issues.apache.org/jira/browse/AMQ-3643
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.5.1
> Environment: vmQueueCursor
> Reporter: Torsten Mielke
> Priority: Critical
> Labels: vmQueueCursor
> Fix For: NEEDS_REVIEWED
>
> Attachments: VMQueueCursorBug.tgz
>
>
> The vmQueueCursor isn't bound to configured memoryUsage limit and hence can
> grow indefinitely and cause OutOfMemoryErrors.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
