There is a lot of relevant detail in https://issues.apache.org/jira/browse/AMQ-6215 and a test case that shows how to best achieve true priority dispatch. It is always a trade off between page in from the store for dispatch (or other reasons to have messages in memory) and prefetch to active consumers.
note some of the scenarios in this test: https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blob;f=activemq-unit-tests/src/test/java/org/apache/activemq/usecases/QueueZeroPrefetchLazyDispatchPriorityTest.java that may help you understand what is in play and point to the best approach. On Thu, 20 Aug 2020 at 07:31, Michel Jung <michel.jun...@gmail.com> wrote: > Hi all, > > My software uses prioritized messages and it's working just fine – until it > doesn't.Some unknown condition leads to my higher prioritized messages not > getting processed until I either remove at least a single message from the > queue, or until all other messages have been processed. > > I posted this on StackOverflow ( > > https://stackoverflow.com/questions/63483621/activemq-why-do-my-messages-get-stuck-in-storequeuecursor > ). > > Is it ok if I just link it rather than repeating it here? > > I'm quite desperate to solve this and would really appreciate it if someone > more competent in this area could point me in the right direction. Thank > you very much. > > Michel >
