You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2015/07/06 16:41:04 UTC

[jira] [Commented] (AMQ-5853) JDBC store - pending high priority messages batch cannot be consumed after low priority message batch

    [ https://issues.apache.org/jira/browse/AMQ-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14615104#comment-14615104 ] 

Gary Tully commented on AMQ-5853:
---------------------------------

fix and additional test in: http://git-wip-us.apache.org/repos/asf/activemq/commit/a2697b84

select clause is now explicit for each [0-9] supported priority wit the store tracking the last recovered sequence.

> 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)