[
https://issues.apache.org/jira/browse/AMQ-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-5853:
-----------------------------
Regression: Regression
There is a problem with the fix, higher priority messages that are dispatched
but where the ack has not yet committed are pulled from the store in error and
are suppressed as duplicates, filling up the DLQ. This is not good.
Am working on a fix.
> JDBC store - pending high priority messages batch cannot be consumed after
> low priority message batch
> ------------------------------------------------------------------------------------------------------
>
> Key: AMQ-5853
> URL: https://issues.apache.org/jira/browse/AMQ-5853
> Project: ActiveMQ
> Issue Type: Bug
> Components: JDBC, Message Store
> Affects Versions: 5.11.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.12.0
>
>
> With priority message enabled a batch of low priority messages can leave the
> cursor unable to load subsequent high priority messages.
> More visible when useCache=false.
> A new consumer or browse will not be able to see pending messages.
> Issue occurs after dispatch of low priority messages, an empty store and the
> addition of high priority messages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
