[
https://issues.apache.org/jira/browse/AMQ-7270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7270.
-----------------------------
Resolution: Fixed
> Queue's copyMatchingMessages effects maxPageSize in error
> ---------------------------------------------------------
>
> Key: AMQ-7270
> URL: https://issues.apache.org/jira/browse/AMQ-7270
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.15.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 5.16.0
>
>
> The copyMatchingMessages jmx op toggles the destination maxPageSize
> attribute. It should not do this b/c it is not thread safe and can effect
> other paging operations like dispatch and purge.
> In addition, concurrent calls to copyMatchingMessages can leave the value at
> queueDepth.
> For large queues, have the maxPageSize == queueDepth means we try and page in
> the entire queue, leading to an OOM.
> For non persistent brokers or where all messages are cached, it is sensible
> to attempt to reference all of the messages in the queue, however in general
> respecting the maxPageSize is advisable.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
