[
https://issues.apache.org/jira/browse/AMQ-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-5853:
-----------------------------
this needs yet another revisit. long lived transactions show that the
limitations of the current approach. The message store needs to keep track of
the last recovered sequence on a per priority basis, in a similar manner to the
topic store. Having the db select from all available messages seems like the
simplest solution b/c the priorities via jms are limited to 0-9
> 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)
