[
https://issues.apache.org/jira/browse/AMQ-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646958#comment-16646958
]
Gary Tully edited comment on AMQ-7070 at 10/12/18 8:18 AM:
-----------------------------------------------------------
my bet is that there is little crossover between tests for priority and the
cache flip tests.
check for tests related to setbatch commits and see to add variants that use
setPrioritizedMessages=true
[~alanprot] The point being that setPrioritizedMessages is disabled by
default, so most of the test do not validate that code path.
One approach to sanity check would be to flip the default for
setPrioritizedMessages to true in PolicyEntry and see if anything gives.
was (Author: gtully):
my bet is that there is little crossover between tests for priority and the
cache flip tests.
check for tests related to setbatch commits and see to add variants that use
setPrioritizedMessages=true
> Priority is not being respected when the cursor cache flips
> -----------------------------------------------------------
>
> Key: AMQ-7070
> URL: https://issues.apache.org/jira/browse/AMQ-7070
> Project: ActiveMQ
> Issue Type: Test
> Components: Broker
> Reporter: Alan Protasio
> Priority: Minor
> Attachments: AMQ7070Test.java
>
>
> Messages are being dispatched with wrong priority when the cache is flipped.
> See:
> https://github.com/apache/activemq/blob/master/activemq-broker/src/main/java/org/apache/activemq/broker/region/cursors/AbstractStoreCursor.java#L258
> All messages that could get cached in the cursor are dispatched before even
> though massages with higher priority is in the cache.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
