[
https://issues.apache.org/jira/browse/AMQ-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613089#comment-14613089
]
Gary Tully edited comment on AMQ-5853 at 7/3/15 10:07 AM:
----------------------------------------------------------
The underlying issue was the tracked last recovered priority. This needed to be
reset in the presence of newly added higher priority messages.
Fix and updated tests in
http://git-wip-us.apache.org/repos/asf/activemq/commit/eece28ac
was (Author: gtully):
The underlying issue was the tracked last recovered priority. This needed to be
reset in the presence of newly added higher priority messages.
Fix and updated tests in
https://fisheye6.atlassian.com/changelog/activemq-git?cs=eece28ac7501103490e1cb7bdc547c07c6968525
> 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
> Priority: Blocker
> 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)
