[
https://issues.apache.org/jira/browse/AMQ-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14593503#comment-14593503
]
Gary Tully edited comment on AMQ-5853 at 7/2/15 9:09 PM:
---------------------------------------------------------
fix in http://git-wip-us.apache.org/repos/asf/activemq/commit/f2a335c2
a next message can have >= last recovered priority and be in sequence or not be
in sequence if it has lower priority.
setter for two statements was missing so not possible to configure via xml.
Sorted now.
was (Author: gtully):
fix in http://git-wip-us.apache.org/repos/asf/activemq/commit/f2a335c2
a next message can have >= last recovered priority and be in sequence or not be
in sequence of it has lower priority.
setter for two statements was missing so not possible to configure via xml.
Sorted now.
> 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)
