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

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 5.11.0
• Fix Version/s: 5.12.0
• Component/s: JDBC, Message Store
• Regression: Regression
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 19/Jun/15 15:05
• Updated: 22/Jan/16 22:46
• Resolved: 06/Jul/15 14:40

Description

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.

Issue Links

• is related to: AMQ-4489 Newly received messages with higher priority are never consumed, until broker is restarted