Ouch. OK. I think a lot of these behaviors might need to be documented a
bit better, or maybe added as edge cases to be fixed in 6.0. I imagine
KahaDB could do this internally but I’m not sure.
I think we might just end up having 2 or 3 queue priorities implemented by
using different physical qu
Was it implemented for topic subscriptions because there is only one
consumer so you don't have to worry about synchronization between threads?
Is that the primary thing that will make implementing this for queues hard?
If so, why is it only available for durable subscriptions but not
non-durable
that is true, the dispatch goes through the cursors in batches once
memory (or the cursor cache) is exhausted.
For durable subs, there is the ability to bypass the paged in messages, see:
https://github.com/apache/activemq/blob/165959e25007271f8cdfdcf72641b9a92483ef40/activemq-unit-tests/src/test/j
No, I was referring to your statement that "due to message cursors, that it
won’t be executed until it’s read into the “maxPageSize window”." I can't
speak to the ability to serve up messages that aren't in the cursor under
those two message stores, though I've never seen anyone refer to such an
a
You mean my statement "KahaDB and LevelDB could probably move it to the
head (I think) but the memory store can not…"
On Mon, May 4, 2015 at 7:31 PM, Tim Bain wrote:
> What you describe matches what I've always understood based on answers from
> people on here (and I've never heard anyone say th
What you describe matches what I've always understood based on answers from
people on here (and I've never heard anyone say that the behavior is
different for any of the data store types), but I can't claim any firsthand
knowledge so if that's not right hopefully someone else will say so.
Tim
On
Let’s say you have a queue with 1M items.. they are all low priority. Then
you add a high priority entry.
I believe, due to message cursors, that it won’t be executed until it’s
read into the “maxPageSize window”.
Is this correct or does it depend on the underlying store?
KahaDB and LevelDB coul
